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.

Bug 1401773

Summary: Start virt-who without env/owner in /etc/virt-who.d/XX will show many traceback info on terminal
Product: Red Hat Enterprise Linux 7 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: Chris Snyder <csnyder>
Status: CLOSED CURRENTRELEASE QA Contact: Eko <hsun>
Severity: low Docs Contact:
Priority: medium    
Version: 7.0CC: khowell, redakkan, yuefliu
Target Milestone: pre-dev-freezeKeywords: Reopened
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: 2020-12-11 11:17:03 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:

Description Liushihui 2016-12-06 03:59:10 UTC
Description of problem:
It hasn't configure env/owner in /etc/virt-who.d/xxx, start virt-who service will show "traceback" info like 
"InvalidOption: Option `env` needs to be set in config `test-esx1`
No handlers could be found for logger "virtwho.main"
"

Version-Release number of selected component (if applicable):
virt-who-0.18-1.el6.noarch
subscription-manager-1.18.5-1.el6.x86_64
python-rhsm-1.18.5-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to stage candlepin/satellite6.2

2. Configure virt-who without env/owner option in /etc/virt-who.d/xxx
[root@nec-em26 rhsm]# cat /etc/virt-who.d/virt 
[test-esx1]
type=esx
server=10.66.79.5
username=Administrator
password=Welcome1!
owner=
env=

3. Restart virt-who service and check info on terminal
[root@nec-em26 rhsm]# service virt-who start
Starting virt-who: Option `env` needs to be set in config `test-esx1`
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/virtwho/__main__.py", line 11, in main
    res = virtwho.main.main()
  File "/usr/lib/python2.6/site-packages/virtwho/main.py", line 125, in main
    executor = Executor(logger, options)
  File "/usr/lib/python2.6/site-packages/virtwho/executor.py", line 63, in __init__
    self.configManager = ConfigManager(self.logger, config_dir)
  File "/usr/lib/python2.6/site-packages/virtwho/config.py", line 399, in __init__
    self._readConfig(parser)
  File "/usr/lib/python2.6/site-packages/virtwho/config.py", line 405, in _readConfig
    config.checkOptions(self.logger)
  File "/usr/lib/python2.6/site-packages/virtwho/config.py", line 304, in checkOptions
    raise InvalidOption("Option `env` needs to be set in config `%s`" % self.name)
InvalidOption: Option `env` needs to be set in config `test-esx1`
No handlers could be found for logger "virtwho.main"
                                                           [FAILED]

Actual results:
It will show many traceback error info on terminal.

Expected results:
It shouldn't show these traceback info on terminal when it hasn't configure env/owner, it should just show info as the following:
[root@hp-dl320egen8-01 ~]# service virt-who start
Starting virt-who: Option --xen-env (or VIRTWHO_XEN_ENV environment variable) needs to be set
                                                           [FAILED]
Additional info:
If it hasn't configure env/owner in /etc/sysconfig/virt-who, it hasn't the problem, it will show remind info as expected result.

Comment 3 Liushihui 2017-03-24 05:37:46 UTC
It also exist on virt-who-0.19-2.el7sat.noarch

Comment 5 Jan Kurik 2017-12-06 12:59:16 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/

Comment 8 Kevin Howell 2017-12-14 15:05:27 UTC
Can you please test if this an issue with the latest virt-who builds?

Comment 9 Liushihui 2017-12-18 05:21:44 UTC
It hasn't this problem on latest virt-who-0.21.2-1.el7.noarch, therefore, verify it.

Comment 10 Rehana 2020-12-11 11:17:03 UTC
Old bug clean up :
================

Closing the bug with Current release ,the bug was verified by QE during a RHEL release cycle but was not closed.