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 1472727 - Virt-who fail to start when configured only one hypervisor with encrypted password but no key file in '/var/lib/virt-who/'
Summary: Virt-who fail to start when configured only one hypervisor with encrypted pas...
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
medium
high
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-19 09:37 UTC by yuefliu
Modified: 2019-10-28 07:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:40:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin virt-who pull 219 0 None None None 2019-05-31 14:45:18 UTC
Red Hat Product Errata RHBA-2019:2070 0 None None None 2019-08-06 12:40:56 UTC

Comment 3 Kevin Howell 2017-07-20 14:22:01 UTC 
Dev: let's make sure virt-who prints a better error message
Comment 4 Liushihui 2017-11-09 07:13:57 UTC 
In virt-who-0.20.4-1.el7sat.noarch, No matter /var/lib/virt-who/key is exist or not, when configure encrypted_password to null or error value(encrypted_password= or encrypted_password=xxxx), failed to start virt-who service and error info as the following:

2017-11-09 06:53:09,370 [virtwho.config ERROR] MainProcess(26373):MainThread @config.py:init_config:1336 - Required option: "password" is missing in: "xen"
2017-11-09 06:53:09,370 [virtwho.init ERROR] MainProcess(26373):MainThread @main.py:main:139 - virt-who can't be started: no valid configuration found

Expected result:
Since configure password to null or error value(password= or password=xxxx), virt-who still can start and error info as the following. when set encrypted_password to null or wrong value, virt-who should be started normally and show the same error info
2017-11-09 07:08:42,153 [virtwho.xen ERROR] MainProcess(26417):Thread-2 @xen.py:login:118 - Unable to login to XENserver https://10.73.131.203
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/xen.py", line 107, in login
    self.session.xenapi.login_with_password(self.username, self.password)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 226, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 122, in xenapi_request
    self._login(methodname, params)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 145, in _login
    result = _parse_result(getattr(self, 'session.%s' % method)(*params))
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 200, in _parse_result
    raise Failure(result['ErrorDescription'])
Failure: ['SESSION_AUTHENTICATION_FAILED', 'root', 'Authentication failure']
2017-11-09 07:08:42,154 [virtwho.xen ERROR] MainProcess(26417):Thread-2 @virt.py:run:383 - Thread 'xen' fails with error: ['SESSION_AUTHENTICATION_FAILED', 'root', 'Authentication failure']
Comment 5 Liushihui 2017-11-09 07:16:37 UTC 
Please ignore comment4 since the virt-who version is wrong. update it as the following:

In virt-who-0.21.0-1.el7.noarch, No matter /var/lib/virt-who/key is exist or not, when configure encrypted_password to null or error value(encrypted_password= or encrypted_password=xxxx), failed to start virt-who service and error info as the following:

2017-11-09 06:53:09,370 [virtwho.config ERROR] MainProcess(26373):MainThread @config.py:init_config:1336 - Required option: "password" is missing in: "xen"
2017-11-09 06:53:09,370 [virtwho.init ERROR] MainProcess(26373):MainThread @main.py:main:139 - virt-who can't be started: no valid configuration found

Expected result:
Since configure password to null or error value(password= or password=xxxx), virt-who still can start and error info as the following. when set encrypted_password to null or wrong value, virt-who should be started normally and show the same error info
2017-11-09 07:08:42,153 [virtwho.xen ERROR] MainProcess(26417):Thread-2 @xen.py:login:118 - Unable to login to XENserver https://10.73.131.203
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/xen.py", line 107, in login
    self.session.xenapi.login_with_password(self.username, self.password)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 226, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 122, in xenapi_request
    self._login(methodname, params)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 145, in _login
    result = _parse_result(getattr(self, 'session.%s' % method)(*params))
  File "/usr/lib/python2.7/site-packages/virtwho/virt/xen/XenAPI.py", line 200, in _parse_result
    raise Failure(result['ErrorDescription'])
Failure: ['SESSION_AUTHENTICATION_FAILED', 'root', 'Authentication failure']
2017-11-09 07:08:42,154 [virtwho.xen ERROR] MainProcess(26417):Thread-2 @virt.py:run:383 - Thread 'xen' fails with error: ['SESSION_AUTHENTICATION_FAILED', 'root', 'Authentication failure']
Comment 6 William Poteat 2019-06-10 19:38:28 UTC 
justification: This error will end the virt-who process. This means that valid data will not be reported on. The proper catching of the exception allows the good data to be reported.
Comment 11 errata-xmlrpc 2019-08-06 12:40:46 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/RHBA-2019:2070
Note You need to log in before you can comment on or make changes to this bug.