Change I81bc48b53068c3a5ed90266a4fd3e62bfb017835 moved image fetching
and tagging for pacemaker-managed services from step 1 to step 2. This
is also a step when the services are started, which probably
introduced a race condition for environments where pacemaker cluster
consists of more than one machine.
During the deployment you can get a lot of pcmk failures like:
failed to pull image 192.168.24.1:8787/tripleomaster/centos-binary-mariadb:pcmklatest
This only happens on non-bootstrap nodes. On bootstrap node the order
is still correct, first download and tag image, and then start the
pcmk resources. However, if non-bootstrap nodes are slower with
downloading and tagging, pacemaker there might start the resources
before the images are tagged (as the starting of resources is
controlled globally from bootstrap node).
Reviewed: https:/ /review. openstack. org/620918 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=3f57d7380d8 ffc6908750efb02 ff2d0221839786
Committed: https:/
Submitter: Zuul
Branch: master
commit 3f57d7380d8ffc6 908750efb02ff2d 0221839786
Author: Jiri Stransky <email address hidden>
Date: Thu Nov 29 12:02:21 2018 +0100
Fix pacemaker tagging race condition
Change I81bc48b53068c3 a5ed90266a4fd3e 62bfb017835 moved image fetching
and tagging for pacemaker-managed services from step 1 to step 2. This
is also a step when the services are started, which probably
introduced a race condition for environments where pacemaker cluster
consists of more than one machine.
During the deployment you can get a lot of pcmk failures like:
failed to pull image 192.168. 24.1:8787/ tripleomaster/ centos- binary- mariadb: pcmklatest
This only happens on non-bootstrap nodes. On bootstrap node the order
is still correct, first download and tag image, and then start the
pcmk resources. However, if non-bootstrap nodes are slower with
downloading and tagging, pacemaker there might start the resources
before the images are tagged (as the starting of resources is
controlled globally from bootstrap node).
Change-Id: Id669cc9a296a83 66c7c80a5ee509b db964b62a04
Closes-Bug: #1805826