Comment 2 for bug 1824993

This bug was only encountered on standalone deployments (1 server deploys with 1 mon). TripleO CI's standalone scenario is still using the workaround in Victoria [1]. What will be Wallaby is not using the workaround [3] as it's using cephadm [4]. The standalone deployment are used for CI jobs with constrained resources (and developer environments).

This bug was never encountered on multinode deployments with supported configurations like 3 monitors.

[1] https://github.com/openstack/tripleo-heat-templates/blob/stable/victoria/ci/environments/scenario001-standalone.yaml#L82

[2] https://github.com/openstack/tripleo-heat-templates/blob/stable/victoria/ci/environments/scenario004-standalone.yaml#L54

[3] https://github.com/openstack/tripleo-heat-templates/blob/master/ci/environments/scenario001-standalone.yaml

[4] https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/tripleo-ceph.html