Description of problem:
The neutronclient should fallback to password entry via tty if no password given from env or --os-password
Version-Release number of selected component (if applicable):
This is present upstream.
Easy to reproduce.
Steps to Reproduce:
1. packstack allinone
2. delete the password line from keystonerc_admin
3. `source keystonerc_admin`
4. `neutron agent-list`
You must provide a password via either --os-password or env[OS_PASSWORD]
Prompt for OS Password as novaclient and keystoneclient do.
I used the method in keystoneclient to make a patch and submitted to upstream.
How do other clients behave here? There needs to be consistency.
Right now there is not consistency.
Nova and Keystone clients both fallback to TTY password entry, although both implement this completely differently.
The seperate "openstack" client also has this feature, and implements it in the same way as the Keystone client.
I used Keystone implementation in my upstream commit.
This has been merged upstream:
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
According to our records, this should be resolved by python-neutronclient-2.4.0-2.el7ost. This build is available now.
Tested on latest OSPd setup: python-neutronclient-2.4.0-1.el7ost