Description of problem: Failed to decrypt encrypted password as it failed to run command "virt-who-password" on RHEVH7.1. Version-Release number of selected component (if applicable): rhevh-vdsm7-7.1-20150402.0.el7ev virt-who-0.11-5.el7.noarch How reproducible: Always Steps to Reproduce: 1. On the CLI: login to rhevh with root, run command of "virt-who-password" [root@hp-z220-04 ~]# virt-who-password /usr/bin/python: can't open file '/usr/share/virt-who/virtwhopassword.py': [Errno 2] No such file or directory Actual results: Failed to run "virt-who-password", it will block us to generate encrypted password Expected results: "virt-who-password" used to generate a "encrypted password" which used to decrypt password. Additional info: This bug isn't exist on RHEL7.1
This bug has blocked virt-who's new function of "decrypt encrypted password", it should be resolved ASAP.
(In reply to Liushihui from comment #1) > This bug has blocked virt-who's new function of "decrypt encrypted > password", it should be resolved ASAP. After confirmed with Shihui entitlement QE, there is virt-who new function on rhel 7.1, see bug 1161607, so rhevh also need to make corresponding adjustment to meet the new function of rhel 7.1. Bug 1161607 - virt-who not able to decrypt encrypted password.
rhevh-vdsm6-6.6-20150402.0 has the same problem.
Liushihui, why is this feature important and what can a user do with it? When is it needed? Moving this to 3.6 for now, if it's urgent, then we can backport that change.
Hi Eabian, Since customers requesting password encryption feature. In the previous version of virt-who, administrator/root's password can show on virt-who's configure file as Plaintext, threaten system's security.Therefore, Customers asked for this new feature. please see the detail on bug 1161604. Thanks. Thanks. Liushihui (In reply to Fabian Deutsch from comment #5) > Liushihui, why is this feature important and what can a user do with it? > When is it needed? > > Moving this to 3.6 for now, if it's urgent, then we can backport that change.
snip from bug 1241820 which is cloned from this bug, "It also exist on Rhev-hypervisor-6-6.7-20150707.0" Fabian, not sure how urgent it is on RHEV, you can see comment 6 to whether we clone it to 3.5.z? Thanks.
*** Bug 1241820 has been marked as a duplicate of this bug. ***
Version-Release number of selected component (if applicable): rhev-hypervisor-7-7.2-20151112.1.e17ev ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch Test Steps: 1. Install rhevh 2. Login rhevh, press "F2" to rescue shell, run command of "virt-who-password" # virt-who-password Test results: 1. "virt-who-password" used to generate a "encrypted_password" which used to decrypt password. # virt-who-password Password: Use following as value for encrypted_password key in the configuration file: 87b09966fb9b12f063b9c5dbef57e0ed So this bug is fixed on rhev-hypervisor-7-7.2-20151112.1.e17ev, I will change the status to verified.
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://rhn.redhat.com/errata/RHBA-2016-0378.html