Red Hat Bugzilla – Bug 890295
Packstack should not fail installation of cinder-vol service if the VG doesn't exist (as cinder-vol may be using plugins)
Last modified: 2016-04-26 11:20:35 EDT
Description of problem: Currently, without the existence of the cinder-volumes VG, installation of Cinder fails. That means that I cannot install Cinder in the hope of using it with an external storage plugin (Nexenta, Netapp, etc.). It should, however, issue a warning about it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The current version of packstack deploys openstack using a specific subset of possible ways to install openstack. I would prefer we explicitly fail (the current behavior) until other plugins are supported. This behavior will ensure the most common use case will have a better experience (because a lot of people would miss a warning). In the future if we were to support plugins and need to remove this test, I think the user should need to explicitly set something to remove the test, so that they are aware of the consequences.
@derekh: This is related but maybe should be filed under a new bug... If you run packstack and select to install cinder, but have not created a cinder-volume VG yet, packstack will fail. It's just a few steps to create a simplistic cinder-volumes VG, but why not automate that via puppet? So basically if cinder-volumes VG does exist, use it. If it doesn't then perhaps one can be created. Perhaps two variables need to be specified in the answer file/interactive: cinder-volumes size in GB and location of the backing store file.
I guess we could use puppet-lvm for this: https://github.com/puppetlabs/puppetlabs-lvm
(In reply to comment #2) > @derekh: This is related but maybe should be filed under a new bug... > > If you run packstack and select to install cinder, but have not created a > cinder-volume VG yet, packstack will fail. It's just a few steps to create > a simplistic cinder-volumes VG, but why not automate that via puppet? > > So basically if cinder-volumes VG does exist, use it. If it doesn't then > perhaps one can be created. Perhaps two variables need to be specified in > the answer file/interactive: cinder-volumes size in GB and location of the > backing store file. I filed bug # 904669 for this specific issue
Fix submitted upstream https://review.openstack.org/#/c/20816/ packstack will now stop running in a more acceptable way (without the traceback to standard out), if we need to support specific plugins then these should be handled on an individual basis.
Verified NVR: openstack-packstack-2012.2.2-1.0.dev408.el6ost.noarch 1. Used a machine with no cinder-volumes preconfigured 2. Modified my answer file: CONFIG_CINDER_VOLUMES_CREATE=n 3. Ran packstack: Installing: Clean Up... [ DONE ] Setting up ssh keys... [ DONE ] OS support check... [ DONE ] Adding pre install manifest entries... [ DONE ] Adding MySQL manifest entries... [ DONE ] Adding QPID manifest entries... [ DONE ] Adding Keystone manifest entries... [ DONE ] Adding Glance Keystone manifest entries... [ DONE ] Adding Glance manifest entries... [ DONE ] Adding Cinder Keystone manifest entries... [ DONE ] Checking if the Cinder server has a cinder-volumes vg... Additional information: * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. * ERROR : The cinder server should contain a cinder-volumes volume group
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/RHSA-2013-0595.html
Removed the release note flag, packstack documentation now covers this option though I need to go back over it to confirm it all lines up. This is tracked separately though.