Red Hat Bugzilla – Bug 985361
packstack doesn't accept all configuration options using CLI
Last modified: 2014-01-09 14:40:52 EST
Created attachment 774727 [details] patch which enables accepting the admin password Description of problem: Packstack can get parameters either form CLI, or from answer file. Not all options are available from CLI. Version-Release number of selected component (if applicable): openstack-packstack-2013.1.1-0.23.dev642.el6ost.noarch How reproducible: 2/2 Steps to Reproduce: 1. [root@rhel-preinstalled ~]# packstack --keystone-admin-passwd 123456 Usage: packstack [options] [--help] packstack: error: no such option: --keystone-admin-passwd Actual results: ERROR Expected results: deployed using the specified password Additional info: To get some clue what should the USE_DEFAULT do, I tried: git grep -C3 'USE_DEFAULT.*False' git grep -C3 'USE_DEFAULT.*True' and compared the results. Not all of the *_PW nor only the *_PW options have USE_DEFAULT=True, but mostly they do. It seems to be used for some sensitive data, but I have no idea what is it's purpose.
Assigning this to Ondra, so he can start with something easy.
My mistake, this is 3.0 bug.
Works: [root@foo ~]# packstack --keystone-admin-passwd=secret [root@foo ~]# grep PASS keystonerc_admin export OS_PASSWORD=secret [root@foo ~]# grep PASS keystonerc_admin export OS_PASSWORD=secret (reverse-i-search)`.': /etc/init^C/sshd restart [root@foo ~]# . keystonerc_admin [root@foo ~(keystone_admin)]# nova list [root@foo ~(keystone_admin)]# keystone token-get +-----------+----------------------------------+ | Property | Value | +-----------+----------------------------------+ | expires | 2013-11-05T07:33:00Z | | id | d6f48e1907ff4e20910f127cca48b038 | | tenant_id | 5cc7ba19dd934003b44fc34a634d9f99 | | user_id | 52589145fe88426aa7dbfb0b70571295 | +-----------+----------------------------------+ [root@foo ~(keystone_admin)]# rpm -q openstack-packstack openstack-packstack-2013.1.1-0.33.dev695.el6ost.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/RHBA-2013-1510.html