Description of problem: this bug is a phase two of bug [1], where we introduced prompt for user/password, password option was hidden from the command-line help, but remained functional so users could easily migrate to the prompt/config-file to specify the password, (command-line option --password is no longer supported for security reasons as mentioned in comments from [1]) [1] 854338 - [rhevm-cli] Add username/password prompt/command-line functionality to RHEV-M CLI [2] https://bugzilla.redhat.com/show_bug.cgi?id=854338#c6
[RHEVM shell (disconnected)]# exit [imeerovi@imeerovi ART]$ rhevm-shell --password foo option "--password" is not supported, see help for more details. [imeerovi@imeerovi ART]$ rhevm-shell -h Usage: rhevm-shell [options] rhevm-shell [options] command... This program is a command-line interface to RHEVM Virtualization. Options: -h, --help show this help message and exit -d, --debug enable debugging -l URL, --url=URL specifies the API entry point URL (http[s]://server[:port]/api) -u USERNAME, --username=USERNAME connect as this user -K KEY_FILE, --key-file=KEY_FILE specify client PEM key-file -C CERT_FILE, --cert-file=CERT_FILE specify client PEM cert-file -A CA_FILE, --ca-file=CA_FILE specify server CA cert-file -I, --insecure allow connecting to SSL sites without CA certificate -D, --dont-validate-cert-chain do not validate server CA certificate -F, --filter enables user permission based filtering -P PORT, --port=PORT specify port -T TIMEOUT, --timeout=TIMEOUT specify request timeout -S SESSION_TIMEOUT, --session-timeout=SESSION_TIMEOUT specify authentication session timeout (0 disables session expiry) -c, --connect automatically connect -f FILE, --file=FILE read commands from FILE instead of stdin -e, --extended-prompt display extra information in the prompt [imeerovi@imeerovi ART]$ rhevm-shell -p foo option "-p" is not supported, see help for more details. [imeerovi@imeerovi ART]$ [imeerovi@imeerovi ART]$ rpm -q rhevm-cli rhevm-cli-3.3.0.5-1.el6ev.noarch
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. http://rhn.redhat.com/errata/RHEA-2014-0076.html