When deploying keystone for the first time, aliveness check inside
service_bootstrap can not succeed for multi-node setup, as playbook
will disable current backend. So we need to bootstrap host only
when running against last host in play. We also should make sure, that
following tasks will not fail when running against first ones.
With that we also now able to check the service status during
bootstrap against the internal VIP. This is important in environments
with limited connectivity.
Reviewed: https:/ /review. opendev. org/c/openstack /openstack- ansible- os_keystone/ +/859232 /opendev. org/openstack/ openstack- ansible- os_keystone/ commit/ 36d06d4cc3c74fb 749ac655f74e350 92d6acea07
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit 36d06d4cc3c74fb 749ac655f74e350 92d6acea07
Author: Dmitriy Rabotyagov <email address hidden>
Date: Mon Sep 19 16:08:46 2022 +0200
Bootstrap when running against last backend
When deploying keystone for the first time, aliveness check inside bootstrap can not succeed for multi-node setup, as playbook
service_
will disable current backend. So we need to bootstrap host only
when running against last host in play. We also should make sure, that
following tasks will not fail when running against first ones.
With that we also now able to check the service status during
bootstrap against the internal VIP. This is important in environments
with limited connectivity.
Closes-Bug: #1990008 aa23b4f40b335c1 41071a56f08
Closes-Bug: #1989326
Squashes Change-ID: I1a4aec40618237
Change-Id: Ifa9a79c34265b2 25a5e24c30cae47 d3f0fa0739f 5574efa66deb217 ab2491d5c2)
(cherry picked from commit 7868766202b8020