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:
2 latest version of virt-who ignore the -c option when run in -o mode.
Version-Release number of selected component (if applicable):
0.17.9,
0.17.10
How reproducible:
Every time we run virt-who -o -c /etc/virt-who.d/<file>
Create 2 configuration files under /etc/virt-who.d/ (eg loc1.conf and loc2.conf)
Steps to Reproduce:
1. Create a configuration file /etc/virt-who.d/loc1.conf
2. Create a second configuration file /etc/virt-who.d/loc2.conf
3. Use ESX mode for both sites
4. Execute virt-who -o -c /etc/virt-who.d/loc1.conf
Actual results:
virt-who **ingores** the -c option and process ALL files under /etc/virt-who.d directory
Expected results:
virt-who should process only the configuration file we set.
Additional info:
In version 0.14.9 works as expected.
Severity is set to high because it can cause issues with subscriptions when ESXi hosts are added in the Satellite.
now virt-who will run all the configure files in /etc/virt-who.d/ by default,
if the file is in /etc/virt-who.d/, with -c or without -c, this file will always be run,
the -c option often be used for the files not in /etc/virt-who.d/,
Hi Chris, do you think this is a bug?
Considering this worked differently in prior versions of virt-who, I would say that this is a bug.
The current behaviour seems to be to add the configuration specified using -c but not to limit the configs used to only those specified using the cli options.
Is the desired behaviour to ignore all configuration in the /etc/virt-who.d directory if given at least one -c option?
Hello,
Even if -c was designed to use files outside of /etc/virt-who.d, it's not documented. And in any case, we need to have a way to run virt-who for only one configuration file.
It's not a option to remove unwanted files from /etc/virt-who.d, run the command and then place the rest of the files back in /etc/virt-who.d.