Red Hat Bugzilla – Bug 1021902
hosted-engine --add-console-password should have interactive option
Last modified: 2014-01-21 11:54:37 EST
Description of problem:
when you want to set console password, you have to write it in commandline option, like "hosted-engine --add-console-password=badpassword"
there should be an option to input password interactively, so it doesn't stay in bash history, scrollback buffer of screen or anywhere else, for example "hosted-engine --add-console-password --interactive"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. hosted-engine --help
2. use --add-console-password as you see it in help
please use same logic as all other utilities for password handling
I think it should be only interactive, using an env var to allow you to automate process for testing if really needed.
vdsClient only accepts a password on the command line, so we'll pass it to it this way anyway and it will be seen with 'ps'. Do we want to also make vdsClient accept passwords using other means?
(In reply to Yedidyah Bar David from comment #3)
> vdsClient only accepts a password on the command line, so we'll pass it to
> it this way anyway and it will be seen with 'ps'. Do we want to also make
> vdsClient accept passwords using other means?
I think it should. Please open a BZ about it on vdsm, we'll update hosted-engine code when they'll fix it.
For now, let's fix this on our command line.
Please avoid using the vdsClient command line. It's broken in so many forms. Since hosted-engine is a python app, importing vdsm.vdscli and using it to contact the running vdsm process is much more robust.
(In reply to Dan Kenigsberg from comment #5)
> Please avoid using the vdsClient command line. It's broken in so many forms.
> Since hosted-engine is a python app, importing vdsm.vdscli and using it to
> contact the running vdsm process is much more robust.
Actually hosted-engine is a shell script. Only ovirt-hosted-engine-setup, which is called by '--deploy', is a python app.
Patches merged on upstream master and 1.0 branches.
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.