Sam Yaple 8f194e50a0 Fixes an issue with AIO and galera clusters
AIO nodes had an address in the gcomm list which would prevent AIO
containers from starting appropriately.

Change-Id: I6db8c831ef9f9c0348748eb9539db326dc0df048
Closes-Bug: #1472481
2015-07-11 09:05:29 +00:00

21 lines
695 B
YAML

---
- include: config.yml
- include: bootstrap.yml
- include: start.yml
# We use register as a test to see whether the database is active and ready to
# communicate. This run on all hosts that have a database and attempts to talk
# to the local database rather than the vip,
- include: register.yml
# This will restart the container we initially used to bootstrap the cluster to
# make it match the other containers environment-wise. This also prevents a
# change from showing up when rerunning the playbooks
- include: start.yml
# Since the last start.yml may have recreated some containers we must wait and
# check the health again to ensure the hosts are active.
- include: register.yml