Boot from Volume fails in OpenStack Ocata and newer

[Frode Nordahl]

Due to this upstream change that landed in Ocata: https://review.openstack.org/#/c/389399/ boot from Volume does not work when OpenStack is deployed using the current version of the charms.

We would need to transfer cinders ceph credentials from cinder unit to nova-compute unit in order for it to install it as a libvirt secret.

[Frode Nordahl (fnordahl)]

Combined with the fact that Ocata Horizon Launch Instance modal now has "Boot from Volume" selected by default, I think this issue is quite important to fix.

[Frode Nordahl (fnordahl)]

Add some log output from Nova Compute for reference and to make it easier to find this bug:
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [req-8f9ff125-d9ef-4cbd-a70c-251d36540619 d5a4449a9821494bbd28f897db98bdd7 05d981a5adbc474b879ce91d6fe25d52 - - -] [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] Instance failed to spawn
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] Traceback (most recent call last):
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2124, in _build_resources
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] yield resources
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1930, in _build_and_run_instance
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] block_device_info=block_device_info)
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2698, in spawn
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] destroy_disks_on_failure=True)
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5114, in _create_domain_and_network
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] destroy_disks_on_failure)
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] self.force_reraise()
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] six.reraise(self.type_, self.value, self.tb)
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5086, in _create_domain_and_network
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] post_xml_callback=post_xml_callback)
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77-ab1ea457c077] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5004, in _create_domain
2017-08-17 07:02:34.064 17701 ERROR nova.compute.manager [instance: d351d349-afe9-4e4f-9f77...

[Frode Nordahl (fnordahl)]

https://etherpad.openstack.org/p/charm-nova-compute-ocata-cinder-ceph-credentials

[Corey Bryant (corey.bryant)]

Is this only a problem in Pike or is it also a problem in Ocata? It looks like https://review.openstack.org/#/c/389399/ was designed to fall-back to the old behavior in Ocata.

[Frode Nordahl (fnordahl)]

It is indeed a problem in Ocata as well because we are configuring rbd_user in cinder.conf. When rbd_user is set in cinder.conf Nova will ignore what is set in nova.conf and use data from cinder instead.

It gets the data from the block_device_mapping table.

[Frode Nordahl (fnordahl)]

This may be a duplicate of bug 1671422 which already holds a fix