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.
Bug 1476894 - Virt-who not filtering the hosts with name and uuid both
Summary: Virt-who not filtering the hosts with name and uuid both
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks: 1441761
TreeView+ depends on / blocked
 
Reported: 2017-07-31 18:02 UTC by Kevin Howell
Modified: 2023-09-15 00:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1441761
Environment:
Last Closed: 2018-06-15 12:59:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Kevin Howell 2017-07-31 18:03:13 UTC
Dev: please reproduce the issue if possible.

Comment 3 Chris Snyder 2017-08-07 18:49:18 UTC
I am not able to reproduce the issue. Virt-who 0.19 is able to parse values of the 'filter_hosts' config parameter correctly.

The filter_hosts configuration parameter will select only hypervisors with hypervisor_ids matching the value(s) given to it.

In my reproducer using the value for 'filter_hosts' of (less the single quotes)
'"abc.caidan.local","xyz.caidan.local"', results in only the hypervisors with hostnames "abc.caidan.local" and "xyz.caidain.local" to be sent.

I've also verified that using a 'filter_hosts' value of (less the single quotes) 'abc.caidan.local,xyz.caidan.local' behaves the same as above as well.

-----------------------------------------------------------------------

It is worth noting that the configuration parameters 'filter_hosts' and similar ('exclude_hosts'), match against whatever the hypervisor_id is set to. So with a 'hypervisor_id' setting of 'hostname', 'filter_hosts' will match the hostnames retrieved from the server.


-----------------------------------------------------------------------

At this point I would suggest removing the 'filter_hosts' parameter (as you have),
setting the 'hypervisor_id' to 'hostname' (as you have), and running the following, to see what virt-who has identified the hostnames as:

'virt-who --print 2>/dev/null | python -m json.tool | grep uuid'

That should help to identify if perhaps there is a mismatch in what virt-who is gathering as the hostnames and what is expected (used in the filter).


Please let me know if you are able to solve the issue using the above.

Comment 9 Jiri Hnidek 2018-06-15 12:59:53 UTC
We are closing this bug report. When more information will be available, then feel free to reopen this bug report.

Comment 10 Red Hat Bugzilla 2023-09-15 00:03:14 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.