Force re-run of pacemaker bundle init containers during upgrade-scaleup
We need to recreate the *_init_bundle containers during the staged
upgrade (upgrade-scaleup), because the init containers will e.g. set
the correct replica count for the bundle as we're scaling up from 1 to
3 controllers.
The init containers wouldn't get re-run/recreated automatically on
upgrade-scaleup because none of their input would change. The
DeploymentIdentifier is set by the `openstack upgrade prepare` command
and applied during upgrade with `--limit controller-0`. Then later
when we run `--limit controller-0,controller-1`, the
DeploymentIdentifier value does not change from the perspective of
controller-0, so we have to explicitly remove the bundle init
containers to force re-running them.
Reviewed: https:/ /review. opendev. org/676173 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=d4db2fa532c 81c7c7ed13f45cb 22d22ed42011bf
Committed: https:/
Submitter: Zuul
Branch: master
commit d4db2fa532c81c7 c7ed13f45cb22d2 2ed42011bf
Author: Jiri Stransky <email address hidden>
Date: Tue Aug 13 13:59:44 2019 +0200
Force re-run of pacemaker bundle init containers during upgrade-scaleup
We need to recreate the *_init_bundle containers during the staged
upgrade (upgrade-scaleup), because the init containers will e.g. set
the correct replica count for the bundle as we're scaling up from 1 to
3 controllers.
The init containers wouldn't get re-run/recreated automatically on dentifier is set by the `openstack upgrade prepare` command 0,controller- 1`, the dentifier value does not change from the perspective of
upgrade-scaleup because none of their input would change. The
DeploymentI
and applied during upgrade with `--limit controller-0`. Then later
when we run `--limit controller-
DeploymentI
controller-0, so we have to explicitly remove the bundle init
containers to force re-running them.
Change-Id: I93c6d7292f3752 9735e24286f4076 634aa4fe6a5
Partial-Bug: #1831690