Description of problem: I got error from packstack that KeyError: 'CONFIG_CINDER_VOLUMES_SIZE' despite the fact that this variable is set in asnwer file. Version-Release number of selected component (if applicable): openstack-packstack-2014.2-0.5.dev1316.g733aa73.el7.centos.noarch How reproducible: always Steps to Reproduce: 1. packstack --answer-file=/root/packstack-controller-answers.txt Actual results: .. Adding Glance manifest entries [ DONE ] Adding Cinder Keystone manifest entries [ DONE ] Adding Cinder manifest entries [ ERROR ] ERROR : 'CONFIG_CINDER_VOLUMES_SIZE' Please check log file /var/tmp/packstack/20141114-181420-pGB2sC/openstack-setup.log for more information Expected results: No errors Additional info: From openstack-setup.log: yum install -y yum-plugin-priorities || true rpm -q epel-release && yum-config-manager --setopt="rhel-server-ost-6-4-rpms.priority=1" --save rhel-server-ost-6-4-rpms yum clean metadata 2014-11-14 18:14:28::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' Relevant part of answer file: # The Cinder backend to use, valid options are: lvm, gluster, nfs, # vmdk CONFIG_CINDER_BACKEND=lvm # Create Cinder's volumes group. This should only be done for testing # on a proof-of-concept installation of Cinder. This will create a # file-backed volume group and is not suitable for production usage. CONFIG_CINDER_VOLUMES_CREATE=n # Cinder's volumes group size. Note that actual volume size will be # extended with 3% more space for VG metadata. CONFIG_CINDER_VOLUMES_SIZE=5G
This issue seems to be fixed in openstack-packstack.noarch 0:2014.2-0.7.dev1340.gd4df05a.fc22 openstack-packstack-puppet.noarch 0:2014.2-0.7.dev1340.gd4df05a.fc22 openstack-puppet-modules.noarch 0:2014.2.4-1.fc22 Feel free to close as those version reach oficial RDO Juno repositories.
Premature joy. It just proceed little bit further and I got: 209.132.184.9_keystone.pp: [ DONE ] 209.132.184.9_glance.pp: [ DONE ] 209.132.184.9_cinder.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 209.132.184.9_cinder.pp Error: Could not find data item CONFIG_CINDER_VOLUMES_SIZE in any Hiera data file and no default supplied at /var/tmp/packstack/b83e3250893c48619411237d763ba06d/manifests/209.132.184.9_cinder.pp:50 on node fed-cloud09.cloud.fedoraproject.org You will find full trace in log /var/tmp/packstack/20141114-184224-lPY0kI/manifests/209.132.184.9_cinder.pp.log Where log just say: Error: NetworkManager is not running. ^[[1;31mError: Could not find data item CONFIG_CINDER_VOLUMES_SIZE in any Hiera data file and no default supplied at /var/tmp/packstack/b83e3250893c48619411237d763ba06d/manifests/209.132.184.9_cinder.pp:50 on node fed-cloud09.cloud.fedoraproject.org^[[0m ^[[1;31mError: Could not find data item CONFIG_CINDER_VOLUMES_SIZE in any Hiera data file and no default supplied at /var/tmp/packstack/b83e3250893c48619411237d763ba06d/manifests/209.132.184.9_cinder.pp:50 on node fed-cloud09.cloud.fedoraproject.org^[[0m
*** Bug 1165570 has been marked as a duplicate of this bug. ***
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.
Looks like the issue is still not fixed: ERROR : Error appeared during Puppet run: 10.10.0.40_cinder.pp Error: Could not find data item CONFIG_CINDER_VOLUMES_SIZE in any Hiera data file and no default supplied at /var/tmp/packstack/b16fbf8753244e378e8f1a8c4548e2d2/manifests/10.10.0.40_cinder.pp :50 on node storage Using the following packages: openstack-puppet-modules-2014.2.4-1.fc22.noarch openstack-packstack-2014.2-0.7.dev1340.gd4df05a.fc22.noarch openstack-packstack-puppet-2014.2-0.7.dev1340.gd4df05a.fc22.noarch
We check for a volume group called cinder-volumes so if the vg name is created with a different name ... it fails with that issue ! I am working on a new patch !
(In reply to Gaël Chamoulaud from comment #6) > We check for a volume group called cinder-volumes so if the vg name is > created with a different name ... it fails with that issue ! > > I am working on a new patch ! Nope it's not correct. it should fail with this message: ERROR : The cinder server should contain a cinder-volumes volume group
Should be fixed with https://review.openstack.org/#/c/136766/
It looks like the last patch still needs work, according to comments in gerrit.
https://review.openstack.org/#/c/136766/3 should fix that issue.
openstack-packstack-2014.2-0.9.dev1359.g40f3b9d.fc22 is available in the public RDO Juno repository
on a plain vanilla SL7.1 box I hit this: ERROR : Error appeared during Puppet run: 192.168.10.19_prescript.pp Error: Could not find data item CONFIG_USE_SUBNETS in any Hiera data file and no default supplied at /var/tmp/packstack/37423ba0aac8497c8116227c28910264/manifests/192.168.10.19_prescript.pp:2 on node work1.ccnr.btch.ceb.private.cam.ac.uk You will find full trace in log /var/tmp/packstack/20151124-145900-d2admn/manifests/192.168.10.19_prescript.pp.log Please check log file /var/tmp/packstack/20151124-145900-d2admn/openstack-setup.log for more information these are rpm deps installed: PyYAML.x86_64 0:3.10-11.el7 libwebp.x86_64 0:0.3.0-3.el7 libyaml.x86_64 0:0.1.4-11.el7_0 openstack-packstack-puppet.noarch 0:2015.2-0.1.dev1654.gcbbf46e.el7 openstack-puppet-modules.noarch 1:7.0.0-1.el7 pyOpenSSL.noarch 0:0.15.1-1.el7 python-cffi.x86_64 0:1.1.2-3.el7 python-cryptography.x86_64 0:1.0-1.el7 python-docutils.noarch 0:0.11-0.2.20130715svn7687.el7 python-enum34.noarch 0:1.0-4.el7 python-idna.noarch 0:2.0-1.el7 python-ipaddress.noarch 0:1.0.7-4.el7 python-netaddr.noarch 0:0.7.18-1.el7 python-pillow.x86_64 0:2.0.0-17.gitd1c6db8.el7 python-ply.noarch 0:3.4-4.el7 python-pyasn1.noarch 0:0.1.6-2.el7 python-pycparser.noarch 0:2.10-1.el7 ruby.x86_64 0:2.0.0.598-25.el7_1 ruby-irb.noarch 0:2.0.0.598-25.el7_1 ruby-libs.x86_64 0:2.0.0.598-25.el7_1 rubygem-bigdecimal.x86_64 0:1.2.0-25.el7_1 rubygem-io-console.x86_64 0:0.4.2-25.el7_1 rubygem-json.x86_64 0:1.7.7-25.el7_1 rubygem-psych.x86_64 0:2.0.0-25.el7_1 rubygem-rdoc.noarch 0:4.0.0-25.el7_1 rubygems.noarch 0:2.0.14-25.el7_1 python-six.noarch 0:1.9.0-1.el7_1
I see that that errors I get may not really relate to the original report, sorry. I'll file a new bug report.