Bug 1426058

Summary: [RFE] request to provide option "--password" for virt-who-password command
Product: Red Hat Enterprise Linux 7 Reporter: Eko <hsun>
Component: virt-whoAssignee: Chris Snyder <csnyder>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact: Yehuda Zimmerman <yzimmerm>
Priority: unspecified    
Version: 7.4CC: csnyder, jherrman, khowell, sgao, shihliu, tselios.petros, yuefliu
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Password options added to *virt-who-password* With this update, the "-p" and "--password" options have been added to the *virt-who-password* utility. This enables the utility to be used in scripts.
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:

Description Eko 2017-02-23 06:46:16 UTC
Description of problem:
some customers want to use virt-who-password in their scripts, but it doesn't support interact, no "-p" or "--password" options, 

please refer to this commit by Marek: 

Steps to Reproduce:
1.  run virt-who-password with --password or -p
# virt-who-password --password admin

Comment 2 Eko 2017-03-15 02:11:20 UTC
*** Bug 1406721 has been marked as a duplicate of this bug. ***

Comment 3 Eko 2017-03-28 05:09:29 UTC
it's fixed in virt-who-0.19-1, should change the status to ON_QA and add it to errata list.

# virt-who-password --help
Usage: virt-who-password

Utility that encrypts passwords for virt-who.

Enter password that should be encrypted. This encrypted password then can be
supplied to virt-who configuration.

This command must be executed as root!

WARNING: root user can still decrypt encrypted passwords!
  -h, --help            show this help message and exit
  -p PASSWORD, --password=PASSWORD

Comment 6 errata-xmlrpc 2017-08-01 19:24:47 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.