New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible fails to detect Nutanix AHV virtualization facts #57732
Comments
Files identified in the description: If these files are inaccurate, please update the |
Did this work in previous versions or Ansible? needs_info |
Doesn't seem to work on previous versions: Tested with rpm packages from releases.ansible.com/ansible/rpm/release/epel-7-x86_64/
ansible 2.4.6.0
ansible 2.2.3.0 (from releases.ansible.com/ansible/rpm/nightly/stable-2.2/epel-7-x86_64/)
|
Thank you for the information. I just wanted to verify this isn't a regression. Please submit a PR that adds support for gathering facts on Nutanix AHV, including tests. |
I just created a PR(#58327). Unfortunately it doesn't include tests, I didn't find any existing unit tests that mock virtual facts. I'll read https://docs.ansible.com/ansible/latest/dev_guide/testing_units.html#testing-units and see if I can come up with unit tests for this. |
So far I haven't had time to create tests for this. Is the PR ok without tests or are tests required ? |
SUMMARY
ansible-2.8.0 doesn't detect virtualization facts when VM is running on Nutanix AHV hypervisor.
ISSUE TYPE
(I created a patch for this: https://github.com/jjh74/ansible/commit/024549e97eaabb12ba7f4787b3bfaa8fb51880a9
if it looks reasonable I can create a pull request).
COMPONENT NAME
module_utils/facts/virtual/linux.py
ANSIBLE VERSION
Same results with:
CONFIGURATION
OS / ENVIRONMENT
When VM is running on Nutanix AHV:
STEPS TO REPRODUCE
ansible -m setup localhost
...
"ansible_virtualization_role": "NA",
"ansible_virtualization_type": "NA",
...
EXPECTED RESULTS
ansible -m setup localhost should return for example:
...
"ansible_virtualization_role": "guest",
"ansible_virtualization_type": "kvm",
...
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: