Don't create cinder_volumes containers on hosts without cinder-volumes VG

Bug #1495687 reported by Tom Cameron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned

Bug Description

Cinder playbooks should skip creating cinder_volumes_container-* on storage hosts that do not have a volume group present for cinder volume creation. This but impacts latest Juno but has not been tested on Kilo.

Example:

Hosts storage01 and storage02 do not have a volume group named "cinder-volumes", while host storage03 does. All three hosts have containers named cinder_volumes_container. Only the volumes container on storage03 is capable of hosting cinder volumes, so the creation of cinder_volumes_container on storage01 and storage02 should be skipped.

Upon future playbook executions, if the volume group is present then the necessary containers() should be created.

Revision history for this message
Darren Birkett (darren-birkett) wrote :

What if the back end isn't lvm? The lack of a cinder-volumes vg should only be a concern when the back end is lvm, so any fix would need to take this into account.

no longer affects: openstack-ansible/trunk
no longer affects: openstack-ansible/juno
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.