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

Solution Verified - Updated

Environment

  • Red Hat Enterprise Linux Server release 7.9 (Maipo)
  • virt-who-0.28.10-1

Issue

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

Resolution

By 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.

This content is not included.Bug 2034969 has been raised to address this behavior.

For more KB articles/solutions related to Virt-who and Virtual Datacenter (VDC) Subscriptions Issues, please refer to the Consolidated Troubleshooting Article for Virt-who and Virtual Datacenter (VDC) Subscriptions Issues

SBR
Product(s)
Components
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.