cinder charm should stop volume service until configured

[Gema Gomez]

When deploying the cinder charm in a standard openstack configuration for ubuntu[1], I am unable to use volumes afterwards:
I found a few issues in the cinder-volume.log file (https://pastebin.canonical.com/121631/), in particular:

 Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings -o name cinder-volumes
2014-12-03 14:54:17.916 29826 TRACE cinder.volume.manager Exit code: 5

[1] http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/default.yaml

Steps to reproduce:

1) deploy with juju-deployer:
 juju-deployer --bootstrap -c default.yaml -d trusty-icehouse --debug
2) look into the cinder-volume.log file:
juju ssh cinder/0
cat /var/log/cinder/cinder-volume.log

[Gema Gomez (gema)]

Adding the file referenced in the description as a pastebin.

[Edward Hope-Morley (hopem)]

Looks like your db was not ready when you joined the relation so cinder-manage did not work

[Edward Hope-Morley (hopem)]

Also looks like cinder is using lvm driver but there is no block storage available to create a vg.

[Edward Hope-Morley (hopem)]

block-device: "None"

[Gema Gomez (gema)]

ubuntu@juju-gema-machine-5:~$ sudo losetup -a
sudo: unable to resolve host juju-gema-machine-5
ubuntu@juju-gema-machine-5:~$ sudo vgs
sudo: unable to resolve host juju-gema-machine-5
  No volume groups found

[Edward Hope-Morley (hopem)]

Having now looked at the deployment I understand what has happened. The errors in the cinder-volume logs about db connections and volume-groups not found are from the time between cinder being installed (install hook) and cinder being configured i.e. config-changed and ceph-relation-joined since you have added ceph as a relation. So, your cinder service is actually working - I was able create a volume successfully and checked that it was created in ceph. The errors you were seeing are a red herring. While things do not appear to actually be broken, we could improve things by ensuring that the cinder-volume service is only started once the config-changed hook has run but, in your case it would not have stopped the errors since you needed the ceph relation to complete for cinder-volume to work properly.

[Gema Gomez (gema)]

Ed, adding test log for the failure that made me look at this particular node of the deployment.