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.

Please make a separate RFE that reflects #3. This will not be changed in the 8.0.0 time frame.

There is a bug already that covers removing the env config references from the documentation and files. https://bugzilla.redhat.com/show_bug.cgi?id=1657104

The answer for this issue is to change over to the configuration files for each fabric in /etc/virt-who.d/*.conf. That is the designed method go forward.

Closing as WONTFIX

Hi William, thanks for your reply, I have opened a new RFE bug based on #3 for RHEL7.7: https://bugzilla.redhat.com/show_bug.cgi?id=1658440

I'm still a little worried about this issue, customer will meet with the confused error message if configure virt-who in /etc/sysconfig/virt-who as usual.