Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionJaskaran Singh Narula
2018-05-14 13:54:31 UTC
Description of problem:
Virt-who does not take regular expression into consideration when it is mentioned in virt-who.conf file as well.
Steps to Reproduce:
1. Set up hypervisors with hostnames as hostnam0202.example.com and hostname02003.example.com
2. Add filter host parameter in the virt-who.conf file as filter_hosts=hostname00[\d\d\d].*
3. check if the hosts are visible on satellite web ui.
Actual results:
No hypervisors are showing up on the satellite web ui or even in one shot of virt-who.
Expected results:
All the hypervisors and guest VMs should come up on satellite and also in one shot of virt-who.
Additional info:
The regex in question is:
filter_hosts=server0[\d\d\d].*
server0 matches the characters server0 literally (case sensitive)
Match a single character present in the list below [\d\d\d]
\d matches a digit (equal to [0-9])
\d matches a digit (equal to [0-9])
\d matches a digit (equal to [0-9])
.* matches any character (except for line terminators)
* Quantifier — Matches between zero and unlimited times, as many times as possible, giving back as needed
As `man virt-who-config` states regex is supported changing it from RFE to BUG.
~~~
filter_hosts
Only hosts which uuid (or hostname or hwuuid, based on hypervisor_id) is specified in comma-separated list in this option will be reported. Wildcards and regular expressions are supported.
Put the value into the double-quotes if it contains special characters (like comma). filter_host_uuids is deprecated alias for this option.
~~~
Dev: let's add a filter_type option, that can be set to either regex or glob. If unset, let's have the current (ambiguous, confusing) behavior (deprecated), with a warning that filter_type should be defined in order to choose one or the other.
So for the customer in comment 4, the solution once implemented will be to set the filter_type to regex to ensure unambiguous parsing.
After we implement it, the customers who want to use regex or glob in " filter_hosts " parameter they should set "filter_type" accordingly, right?
There are few customers who use Regex in the hypervisor names while filtering so adding this option will help them but can we please make sure it will not break anything for other customers who are using plain hostnames / UUIDs.
The cause of this is from the way ini files are handled.
A backslash needs to be escaped i.e.:
filter_hosts=server0[\\d\\d\\d].*
This is not a bug with virt-who.