Upgrade N->O is broken due to glance registry removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steven Hardy |
Bug Description
We completely removed glance registry in 4ccb27a but that fails to account for upgrades, where e.g newton users will have the service running, and the glance-
This means anyone with OS::TripleO:
Instead, lets stop and disable the service via the new composable service interface, then in pike we can map OS::TripleO:
Changed in tripleo: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Steven Hardy (shardy) |
milestone: | none → ocata-rc1 |
Reviewed: https:/ /review. openstack. org/424795 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=4f4582e1b71 37931bc9142e7c9 462b3c854d68dd
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4f4582e1b713793 1bc9142e7c9462b 3c854d68dd
Author: Steven Hardy <email address hidden>
Date: Tue Jan 24 18:46:27 2017 +0000
Add glance registry service to disable on upgrade
We've broken the upgrade job because anyone upgrading with the registry. yaml defined in heat.
glance registry deployed (and defined in their *Services parameters)
will try to deploy with the old glance-
Instead we define a template which stops and disables the service on
upgrade.
Closes-Bug: #1659079 ae2be06811375d1 6611fa45973
Change-Id: I03561954d794af