Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Running virt-who against a HyperV hypervisor fails to collect the host to guest mapping, and ends up displaying a traceback like this:
======
2019-04-30 07:24:53,261 [virtwho.main ERROR] MainProcess(69762):Thread-7 @virt.py:run:397 - Thread 'virt-who-config-14' fails with exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 388, in run
self._run()
File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 343, in _run
data_to_send = self._get_data()
--
return HostGuestAssociationReport(self.config, self.getHostGuestMapping())
File "/usr/lib/python2.7/site-packages/virtwho/virt/hyperv/hyperv.py", line 601, in getHostGuestMapping
guests.append(virt.Guest(HyperV.decodeWinUUID(uuid), self.CONFIG_TYPE, state))
File "/usr/lib/python2.7/site-packages/virtwho/virt/hyperv/hyperv.py", line 531, in decodeWinUUID
if uuid[0] == "{":
TypeError: 'NoneType' object has no attribute '__getitem__'
======
Version-Release number of selected component (if applicable):
virt-who-0.22.5-1.el7.noarch
How reproducible:
Every time if the hypervisor being mapped by virt-who contains an instance without a BIOSGUID field.
Steps to Reproduce:
1. Set up virt-who to communicate with a hyperV hypervisor that contains an instance without a BIOSGUID field.
2. Run the virt-who service or `virt-who -o` on the command line
Actual results:
The virt-who thread gathering mapping info from this individual hyperV fails with the traceback above.
Expected results:
Virt-who would be able to handle a missing BIOSGUID field and either discard the instance from its mapping report or fail gracefully.
Additional info:
--
Description of problem: Running virt-who against a HyperV hypervisor fails to collect the host to guest mapping, and ends up displaying a traceback like this: ====== 2019-04-30 07:24:53,261 [virtwho.main ERROR] MainProcess(69762):Thread-7 @virt.py:run:397 - Thread 'virt-who-config-14' fails with exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 388, in run self._run() File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 343, in _run data_to_send = self._get_data() -- return HostGuestAssociationReport(self.config, self.getHostGuestMapping()) File "/usr/lib/python2.7/site-packages/virtwho/virt/hyperv/hyperv.py", line 601, in getHostGuestMapping guests.append(virt.Guest(HyperV.decodeWinUUID(uuid), self.CONFIG_TYPE, state)) File "/usr/lib/python2.7/site-packages/virtwho/virt/hyperv/hyperv.py", line 531, in decodeWinUUID if uuid[0] == "{": TypeError: 'NoneType' object has no attribute '__getitem__' ====== Version-Release number of selected component (if applicable): virt-who-0.22.5-1.el7.noarch How reproducible: Every time if the hypervisor being mapped by virt-who contains an instance without a BIOSGUID field. Steps to Reproduce: 1. Set up virt-who to communicate with a hyperV hypervisor that contains an instance without a BIOSGUID field. 2. Run the virt-who service or `virt-who -o` on the command line Actual results: The virt-who thread gathering mapping info from this individual hyperV fails with the traceback above. Expected results: Virt-who would be able to handle a missing BIOSGUID field and either discard the instance from its mapping report or fail gracefully. Additional info: --