RUNNING HANDLER [mariadb : wait for slave mariadb] ******************************************************************************************************************************************************************************************************************************************************************************************************
FAILED - RETRYING: wait for slave mariadb (10 retries left).
FAILED - RETRYING: wait for slave mariadb (10 retries left).
FAILED - RETRYING: wait for slave mariadb (9 retries left).
FAILED - RETRYING: wait for slave mariadb (9 retries left).
FAILED - RETRYING: wait for slave mariadb (8 retries left).
FAILED - RETRYING: wait for slave mariadb (8 retries left).
FAILED - RETRYING: wait for slave mariadb (7 retries left).
FAILED - RETRYING: wait for slave mariadb (7 retries left).
...
I think that the point where the logs (as above) show connection refused is parallel to the "FAILED - RETRYING: wait first mariadb container (10 retries left)." ... which kolla then seems to think it's recovered from.
Still haven't been able to sort this out.
Will note that my output when doing a kolla-ansible deploy looks like the following:
RUNNING HANDLER [mariadb : Starting first MariaDB container] ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* **** 01-03.maas]
changed: [idia-ctrl-
RUNNING HANDLER [mariadb : wait first mariadb container] ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* * 01-03.maas]
FAILED - RETRYING: wait first mariadb container (10 retries left).
ok: [idia-ctrl-
RUNNING HANDLER [mariadb : restart slave mariadb] ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* * 01-03.maas] 01-05.maas] 01-04.maas]
skipping: [idia-ctrl-
changed: [idia-comp-
changed: [idia-ctrl-
RUNNING HANDLER [mariadb : wait for slave mariadb] ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* ******* *******
FAILED - RETRYING: wait for slave mariadb (10 retries left).
FAILED - RETRYING: wait for slave mariadb (10 retries left).
FAILED - RETRYING: wait for slave mariadb (9 retries left).
FAILED - RETRYING: wait for slave mariadb (9 retries left).
FAILED - RETRYING: wait for slave mariadb (8 retries left).
FAILED - RETRYING: wait for slave mariadb (8 retries left).
FAILED - RETRYING: wait for slave mariadb (7 retries left).
FAILED - RETRYING: wait for slave mariadb (7 retries left).
...
I think that the point where the logs (as above) show connection refused is parallel to the "FAILED - RETRYING: wait first mariadb container (10 retries left)." ... which kolla then seems to think it's recovered from.