Comment 4 for bug 1724636

OK so When looking at http://logs.openstack.org/25/500625/15/check/legacy-tripleo-ci-centos-7-containers-multinode-upgrades/2a547a7/logs/subnode-2/var/log/messages.txt.gz, I don't see any mention of a container "mysql_data_ownership" which should have been started to chown /var/lib/mysql for containers. It has not been run.

Likewise, looking at http://logs.openstack.org/25/500625/15/check/legacy-tripleo-ci-centos-7-containers-multinode-upgrades/2a547a7/logs/subnode-2/var/log/cluster/corosync.log.txt.gz, I don't see any mention of pacemaker starting any containerized galera on its own.

So I think this upgrade job is not doing the thing it is intended to? If it's a multinode upgrade, it should use the containerized pacemaker settings, i.e. the contents of docker-ha.yaml should be passed to the deploy command.