Description of problem: When running a multi-node packstack install, you get: 2014-03-25 11:15:41::INFO::shell::78::root:: [10.8.0.50] Executing script: echo $HOME 2014-03-25 11:15:41::ERROR::run_setup::907::root:: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 891, in main single_step_install(options) File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 690, in single_step_install _main(answerfilepath) File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 574, in _main runSequences() File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 553, in runSequences controller.runAllSequences() File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 84, in runAllSequences sequence.run(self.CONF) File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 96, in run step.run(config=config) File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 43, in run raise SequenceError(str(ex)) SequenceError: 'CONFIG_PROVISION_DEMO_FLOATRANGE' Version-Release number of selected component (if applicable): Using RDO test day version of M-3: openstack-packstack-2014.1.1-0.4.dev1018.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Run for example: packstack --install-hosts 10.8.0.50,10.8.0.53 Actual results: ERROR : 'CONFIG_PROVISION_DEMO_FLOATRANGE' Please check log file /var/tmp/packstack/20140325-111530-hJiaOR/openstack-setup.log for more information Expected results: In the answers file, it should be: CONFIG_PROVISION_DEMO=n Additional info: To work around this issue, set CONFIG_PROVISION_DEMO=n in the answers file
The error is reproducible even if you set CONFIG_PROVISION_DEMO=n platform: RHEL 7.0 packstack rpms: - openstack-packstack-puppet-2014.1.1-0.7.dev1018.el7.noarch - openstack-packstack-2014.1.1-0.7.dev1018.el7.noarch
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
It looks like this was fixed in 2015 so can be closed?