Bug 1372620
| Summary: | It show "Traceback" info when run virt-who in CLI without env/owner at remote libvirt mode | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Liushihui <shihliu> |
| Component: | virt-who | Assignee: | Chris Snyder <csnyder> |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | ldai, sgao, yuefliu |
| 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: | 2017-08-01 19:24:47 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: | |||
Fixed upstream: https://github.com/virt-who/virt-who/commit/74fb593279d3dc4fcfca41cc928d25ff2bc7cb94 As this has been fixed upstream, it will be fixed in rhel 7.4 as a part o the rebase on upstream. The fix should be included in the first build. As such I'm moving this bug to the MODIFIED state. 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/RHBA-2017:2084 |
Description of problem: When virt-who run with CLI at remote libvirt mode without env/owner, it will show "Traceback (most recent call last):" in terminal. Version-Release number of selected component (if applicable): virt-who-0.17-10.el7.noarch subscription-manager-1.17.11-1.el7.x86_64 python-rhsm-1.17.7-1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Register system to satellite6.2 2. Run virt-who with CLI without env/owner in remote libvirt mode. [root@hp-z220-08 virt-who.d]# virt-who --libvirt --libvirt-owner=111 --libvirt-env= --libvirt-server=hp-z220-06.qe.lab.eng.nay.redhat.com --libvirt-username=root --libvirt-password= -d --satellite6 Option `env` needs to be set in config `env/cmdline` Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtwho/__main__.py", line 8, in main res = virtwho.main.main() File "/usr/lib/python2.7/site-packages/virtwho/main.py", line 132, in main config.checkOptions(logger) File "/usr/lib/python2.7/site-packages/virtwho/config.py", line 291, in checkOptions raise InvalidOption("Option `env` needs to be set in config `%s`" % (self.name)) InvalidOption: Option `env` needs to be set in config `env/cmdline` No handlers could be found for logger "virtwho.main" 2016-09-02 04:34:04,081 [virtwho.init DEBUG] MainProcess(1345):MainThread @executor.py:terminate:303 - virt-who is shutting down Actual results: It will show some traceback info in terminal. Expected results: It shouldn't show traceback info in terminal, it should only show remind info as the following: Option --libvirt-env (or VIRTWHO_LIBVIRT_ENV environment variable) needs to be set Additional info: It hasn't this problem when virt-who run at hyperv mode in the same condition: [root@hp-z220-08 virt-who.d]# virt-who --hyperv --hyperv-env=Library --hyperv-server=10.73.131.228 --hyperv-username=administrator --hyperv-password=Welcome1 -o -d Option --hyperv-owner (or VIRTWHO_HYPERV_OWNER environment variable) needs to be set