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 1458184 - Virt-who can't be started when username option is none/null under /etc/sysconfig/virt-who.
Summary: Virt-who can't be started when username option is none/null under /etc/syscon...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-02 08:58 UTC by yuefliu
Modified: 2019-10-28 07:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 16:19:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github virt-who virt-who pull 79 0 None None None 2017-06-23 21:42:28 UTC
Red Hat Product Errata RHEA-2018:0895 0 None None None 2018-04-10 16:21:04 UTC

Comment 2 Kevin Howell 2017-06-05 14:25:04 UTC 
May be fixed with fix for bug 1457101. (Dev: please verify)
Comment 3 Chris Snyder 2017-06-13 02:48:26 UTC 
This bug was not fixed in the fix for bug 1457101.
Comment 4 Chris Snyder 2017-06-28 17:03:49 UTC 
The proposed fix has been merged upstream. It should be included in the first build for RHEL 7.5. Moving to MODIFIED.
Comment 5 yuefliu 2017-08-01 06:44:45 UTC 
Checked with virt-who-0.20.4-1.el7sat.noarch, the bug can be fixed, will verify it in the first build of rhel7.5.

When configured one hypervisor mode in /etc/sysconfig/virt-who with "VIRTWHO_HYPERV_USERNAME" is none or null, and configured another hypervisor conf file in /etc/virt-who.d/test-esx.conf, virt-who will succeed to be started and send [test-esx] mapping normally, just fail to run HYPERV mode with error:

Error: reading environment variables for virt. type: hyperv: Required env. variable: 'VIRTWHO_HYPERV_USERNAME' is not set.
Comment 10 errata-xmlrpc 2018-04-10 16:19:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0895
Note You need to log in before you can comment on or make changes to this bug.