Comment 3 for bug 1816842

The issue with mariadb-server-0 is a known issue. The problem is related to the design of the openstack-helm chart. Basically they're prioritizing data integrity over coming back into service, so when we're starting up a new mariadb cluster (i.e. there is no running server to join) then as long as one of the mariadb-server pods is not updating the state configmap the other mariadb-server pods will not come up. We plan on adding a monitor to deal with this case after a certain amount of time.

The issue with mariadb-server-1 is unknown at this point...need to figure out why it stopped updating the state configmap. Is the above the full logs from mariadb-server-1?