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:
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
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