glance backend incorrect

[Britt Houser]

Just did an compressed_ha install and had some issues with glance. The default user.compressed_ha.yaml file sets the glance backend to rbd:

--
# grep -R glance_backend /etc/puppet/data/
/etc/puppet/data/class_groups/glance_all.yaml: - "glance::backend::%{glance_backend}"
/etc/puppet/data/global_hiera_params/scenario/compressed_ha.yaml:glance_backend: swift
/etc/puppet/data/global_hiera_params/scenario/full_ha.yaml:glance_backend: swift
/etc/puppet/data/global_hiera_params/common.yaml:glance_backend: file
/etc/puppet/data/hiera_data/user.compressed_ha.yaml:glance_backend: rbd
/etc/puppet/data/hiera_data/user.common.yaml:#glance_backend: rbd
/etc/puppet/data/README.md: + *glance_backend* Selects the backend that should be used by glance
--

However, when I deployed my control nodes, they were showing up as swift for the default_store.

--
# grep default_store /etc/glance/glance-api.conf
default_store = swift
--

When I edit global_hiera_params/scenario/compressed_ha.yaml and set the glance_backend to rbd:

--
sed -i 's/glance_backend.*/glance_backend: rbd/g' /etc/puppet/data/global_hiera_params/scenario/compressed_ha.yaml
puppet apply /etc/puppet/manifests/site.pp
--

then puppet updates my control nodes it sets it to rbd.

--
puppet agent -td --server=cvf3-server-a15.cisco.com
# grep default_store /etc/glance/glance-api.conf
default_store = rbd
--

So its as if the user.compressed_ha.yaml is not overriding global_hiera_params/scenario/compressed_ha.yaml. The default hiera.yaml files reads as follows:

--
:hierarchy:
  - "hostname/%{hostname}"
  - "client/%{clientcert}"
  - user
  - jenkins
  - vendor/cisco_coi_user.%{scenario}
  - user.%{scenario}
--

I actually don't even see the global_hiera_params listed in the hierarchy, so I'm not sure where/how its able to overried user.scenario.

thx,
britt

[subconscious (subconscious)]

I ran multiple installs and confirmed this behavior. The workaround is documented on the install wiki http://docwiki.cisco.com/wiki/Openstack:Havana-Openstack-Installer

From what I can tell so far, the fix (not sure what that is yet) is going to land in scenario_node_terminus.

[Chris Ricker (chris-ricker)]

See also https://bugs.launchpad.net/openstack-cisco/+bug/1275757 (closed as duplicate)

This appears universal to all scenarios, and appears to be that global_hiera_params/scenario/$scenario.yaml settings, if extant, override anything else. Deleting the setting from global_hiera_params/scenario/$scenario.yaml lets the one defined in hiera_data/user.$whatever.yaml be applied

Not sure if this is a bug, or an intended behavior (as I could see the global_hiera_params being useful as a way of saying, for example, in a full_ha scenario you have to use X. No choices about it) and the solution is to delete from global_hiera_params/scenario/$scenario.yaml anything that should really be configurable for that scenario?

[subconscious (subconscious)]

RBD settings removed from global_hiera_data. This should allow the settings in user.compressed_ha.yaml be entered correctly in the hierarchy.

https://github.com/CiscoSystems/puppet_openstack_builder/pull/61

[Chris Ricker (chris-ricker)]

https://github.com/CiscoSystems/puppet_openstack_builder/pull/61 covered full_ha also