Description of problem: I already have a cinder volume group (based on LVM), I don't want packstack to create a new one. Version-Release number of selected component (if applicable): openstack-packstack-2014.2-0.5.dev1316.g733aa73.el7.centos.noarch it worked in the past. cat packst-juno.txt | grep CINDER_VOLUMES CONFIG_CINDER_VOLUMES_CREATE=n CONFIG_CINDER_VOLUMES_SIZE=20G each time, oackstack errors out: Adding Cinder manifest entries [ ERROR ] ERROR : 'CONFIG_CINDER_VOLUMES_SIZE' Please check log file /var/tmp/packstack/20141119-094841-pEUQ2V/openstack-setup.log for more information Log file: 2014-11-19 10:00:52::ERROR::run_setup::955::root:: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 950, in main _main(options,confFile) File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 619, in _main runSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 592, in runSequences controller.runAllSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 68, in runAllSequences sequence.run(config=self.CONF, messages=self.MESSAGES) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 98, in run step.run(config=config, messages=messages) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 38, in run self.function(config, messages) File "/usr/lib/python2.7/site-packages/packstack/plugins/cinder_250.py", line 736, in create_manifest manifestdata += getManifestTemplate('cinder_%s.pp' % backend) File "/usr/lib/python2.7/site-packages/packstack/modules/ospluginutils.py", line 76, in getManifestTemplate return fp.read() % controller.CONF KeyError: 'CONFIG_CINDER_VOLUMES_SIZE'
This issue will be fixed with this patch https://review.openstack.org/#/c/131803/ It has been included in openstack-packstack-2014.2-0.6.dev1331.g34ecfce build. We need to push new build for EPEL-7-JUNO.
*** This bug has been marked as a duplicate of bug 1164359 ***