For what it's worth, I just reproduced this and dug into why it was breaking for me. Sam was correct about the database not being up and for me the container had failed and exited. The reason why was due to improper selinux labeling on /etc/kolla/mariadb/galera.cnf:
Once fixed, I was able to proceed with my minimal deployment. Although this file is not the only one mislabeled, I think this can be closed if it's confirmed the reporter was running with selinux enforcing as well. Or alternatively, maybe we should consider supporting selinux (I assume we don't currently).
For what it's worth, I just reproduced this and dug into why it was breaking for me. Sam was correct about the database not being up and for me the container had failed and exited. The reason why was due to improper selinux labeling on /etc/kolla/ mariadb/ galera. cnf:
restorecon reset /etc/kolla/ mariadb/ galera. cnf context unconfined_ u:object_ r:user_ home_t: s0->unconfined_ u:object_ r:etc_t: s0
Once fixed, I was able to proceed with my minimal deployment. Although this file is not the only one mislabeled, I think this can be closed if it's confirmed the reporter was running with selinux enforcing as well. Or alternatively, maybe we should consider supporting selinux (I assume we don't currently).