Add glance registry service to disable on upgrade
authorSteven Hardy <shardy@redhat.com>
Tue, 24 Jan 2017 18:46:27 +0000 (18:46 +0000)
committerSteven Hardy <shardy@redhat.com>
Tue, 24 Jan 2017 21:33:08 +0000 (21:33 +0000)
commit4f4582e1b7137931bc9142e7c9462b3c854d68dd
treedc68fa501b13d3c7d561d526b30a086874de47d2
parent7020a724049eb7b5f8bfbc503e5a233f97eadb32
Add glance registry service to disable on upgrade

We've broken the upgrade job because anyone upgrading with the
glance registry deployed (and defined in their *Services parameters)
will try to deploy with the old glance-registry.yaml defined in heat.

Instead we define a template which stops and disables the service on
upgrade.

Closes-Bug: #1659079
Change-Id: I03561954d794afae2be06811375d16611fa45973
overcloud-resource-registry-puppet.j2.yaml
puppet/services/disabled/glance-registry.yaml [new file with mode: 0644]