Red Hat Bugzilla – 2034969 – Virt-who parameters 'filter_host_parents' and 'filter_hosts' do not behave as expected when set in a single /etc/virt-who.d/virt-who-config-X.conf file
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.
Virt-who parameters 'filter_host_parents' and 'filter_hosts' do not behave as expected when set in a single /etc/virt-who.d/virt-who-config-X.conf file
Description of problem:
-----------------------
Setting the Virt-who parameter 'filter_hosts' along with the 'filter_host_parents' parameter in a single /etc/virt-who.d/virt-who-config-X.conf file, Virt-who does not identify hypervisors and guests on both the ESX clusters as well as the standalone ESX hosts:
~~~
# tail -f /var/log/rhsm/rhsm.log
2021-12-14 18:14:05,221 [INFO] @virt.py:651 - Hosts-to-guests mapping for config "virt-who-config-3": 0 hypervisors and 0 guests found
~~~
Whereas setting the 'filter_hosts' and 'filter_host_parents' Virt-who parameters in separate /etc/virt-who.d/virt-who-config-X.conf files, Virt-who creates the host-to-guest mapping for both the ESX clusters and standalone ESX hosts specified in the filters.
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
- Red Hat Enterprise Linux Server release 7.9 (Maipo)
- virt-who-0.28.10-1
How reproducible:
-----------------
In customer's infrastructure. Did not reproduce in test lab.
Steps to Reproduce:
-------------------
Configure Virt-who with both 'filter_hosts' and 'filter_host_parents' parameters in a single /etc/virt-who.d/virt-who-config-X.conf file.
Actual results:
---------------
Virt-who does not identify hypervisors and guests on both the ESX clusters as well as the standalone ESX hosts:
~~~
# tail -f /var/log/rhsm/rhsm.log
2021-12-14 18:14:05,221 [INFO] @virt.py:651 - Hosts-to-guests mapping for config "virt-who-config-3": 0 hypervisors and 0 guests found
~~~
Expected results:
-----------------
Virt-who identifies both ESX clusters as well as ESX standalone hosts specified in the filters in the same /etc/virt-who.d/virt-who-config-X.conf file.
As per the discussion with Engineering team and CEE , the customer needs were satisfied by the workaround provided hence no additional z release is needed. Hence closing the bug