Bug 1458184
| Summary: | Virt-who can't be started when username option is none/null under /etc/sysconfig/virt-who. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | yuefliu <yuefliu> |
| Component: | virt-who | Assignee: | Jiri Hnidek <jhnidek> |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | csnyder, hsun, jhnidek, khowell, yanpliu |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 16:19:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 2
Kevin Howell
2017-06-05 14:25:04 UTC
This bug was not fixed in the fix for bug 1457101. The proposed fix has been merged upstream. It should be included in the first build for RHEL 7.5. Moving to MODIFIED. 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. 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 |