Red Hat Bugzilla – Bug 1259354
When pre-creating a vg of cinder-volumes packstack fails with an error
Last modified: 2016-04-26 17:25:09 EDT
Description of problem:
packstack fails when pre-defined cinder-volumes volume group has been created.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install 'clean' centos v7 minimal server
2. Add volume group cinder-volumes
3. run packstack --allinone
192.168.1.100_keystone.pp: [ DONE ]
192.168.1.100_glance.pp: [ DONE ]
192.168.1.100_cinder.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]
ERROR : Error appeared during Puppet run: 192.168.1.100_cinder.pp
Error: /Stage[main]/Cinder::Setup_test_volume/Exec[vgcreate cinder-volumes /dev/loop2]: Failed to call refresh: vgcreate cinder-volumes /dev/loop2 returned 5 instead of one of 
The packstack utility expects storage for use with Cinder to be available on a volume group named cinder-volumes. If this volume group does not already exist then packstack is able to create it automatically
I have been asked to set the flag at
CONFIG_CINDER_VOLUMES_CREATE --cinder-volumes-create y
to n and retry.
asked for log file... as unsure, have uploaded everything from /var/tmp/packstack to http://phillw.net/20150902-154340-iMzKI_/
As asked, I reinstalled the server and created a VG cinder-volumes and then an answer.txt file. I altered CONFIG_CINDER_VOLUMES_CREATE --cinder-volumes-create y
to n as requested and the install using the command
[root@localhost ~]# packstack --answer-file=./answers.txt
did not error out.
creating a new volume of 100 GB worked okay, so the initial limit of 20GB has been resolved.
Tested --allinone with packstack from source and didn't reproduce the problem, i'm gonna test using current kilo package: openstack-packstack-2015.1-0.11.dev1616.g5526c38.fc23
If the problem persists you can set CONFIG_CINDER_VOLUMES_CREATE=n so you can create manually the volume withouht any problem.
is this a desired solution?
Sorry i missed to mention that in comment 2 the OP talks about this solution so i closing this bug.
The bug is not fixed, what we have is a workaround. If you do not know of this link, you cannot pass the 20GB limit. The release notes need editing, or the bug still needs fixing. Fixing the bug is always the preferred way as we know people do not read the release notes :D