The Block Storage service (openstack-cinder-volumes) is initialized earlier in the boot process than items listed in the rc.local file.
On systems deployed by PackStack and configured to use a volume group backed by loopback device for block storage this meant that the volume group was not available when the Block Storage service was started on boot. As a result the service would fail to start.
PackStack has been updated and now ensures that the Block Storage service is restarted once the rc.local file is processed and the volume group is available. This ensures that the Block Storage service continues to function correctly following reboot.
Description of problem:
when installing via packstack, after a reboot, the openstack-cinder-volume service fails to start with:
> VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: volume group cinder-volumes doesn't exist
later in the boot process rc.local enables the volume group as expected, so a service restart fixes this
Version-Release number of selected component (if applicable):
openstack-packstack-2013.1.1-0.17.dev631.el6ost.noarch
openstack-cinder-2013.1.2-3.el6ost.noarch
Steps to Reproduce:
1. install using packstack and using a loopback file for cinder lvm
2. reboot
Actual results:
cinder-volume service is not active
Solution on Packstack side could be:
<mmagr> giulivo, so what do you suggest? add service restart to rc.local?
<giulivo> oh
<giulivo> yeah that is simple and effective :)
<giulivo> packstack could do it, if using a loopback device
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/RHBA-2013-0968.html
Description of problem: when installing via packstack, after a reboot, the openstack-cinder-volume service fails to start with: > VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: volume group cinder-volumes doesn't exist later in the boot process rc.local enables the volume group as expected, so a service restart fixes this Version-Release number of selected component (if applicable): openstack-packstack-2013.1.1-0.17.dev631.el6ost.noarch openstack-cinder-2013.1.2-3.el6ost.noarch Steps to Reproduce: 1. install using packstack and using a loopback file for cinder lvm 2. reboot Actual results: cinder-volume service is not active