It's possible that in CI environment or in slow servers the systemd
reload takes time to read new systemd services and reload systemd while
Ansible already moved on and tries to enable these services.
Adding a retry mechanism so we retry 5 times with a delay of 5 seconds
between, until systemd service returns success as a result.
Change-Id: I2bb39d2aae68a0eadaad92cf0fc4e3506fbfc9ca
Closes-Bug: #1873453
(cherry picked from commit 6e71ea60b659485e08d02cff7a9966c14c36a88b)
Reviewed: https:/ /review. opendev. org/721332 /git.openstack. org/cgit/ openstack/ tripleo- ansible/ commit/ ?id=4e903e2fcf5 24e3baee73974ca e333275cb2c4e9
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 4e903e2fcf524e3 baee73974cae333 275cb2c4e9
Author: Emilien Macchi <email address hidden>
Date: Fri Apr 17 09:06:36 2020 -0400
tripleo_ container_ manage/ systemd: add retries mechanism
It's possible that in CI environment or in slow servers the systemd
reload takes time to read new systemd services and reload systemd while
Ansible already moved on and tries to enable these services.
Adding a retry mechanism so we retry 5 times with a delay of 5 seconds
between, until systemd service returns success as a result.
Change-Id: I2bb39d2aae68a0 eadaad92cf0fc4e 3506fbfc9ca e08d02cff7a9966 c14c36a88b)
Closes-Bug: #1873453
(cherry picked from commit 6e71ea60b659485