+++ This bug was initially created as a clone of Bug #2246440 +++ The main issue is a problematic cephadm code path [1] where we try to verify all the IP addresses associated with a port during the RGW reconfiguration, while it should only look for specific networks. [1] https://github.com/ceph/ceph/blob/v16.2.15/src/cephadm/cephadm#L1304
Regarding the alertmanager issue, it seems that it is the same as with RGW. The spec contains the network list, but when alertmanager first comes up it looks like it is doing a check on *:9093. If it passes, then it binds to the network in the list. But it will fail if opentack's haproxy is running on that port on a different network due to the initial check. The workaround is to stop openstack's haproxy to allow alertmanager to make its check and come up bound on the network, then start haproxy again.
Regarding alertmanager: see https://bugzilla.redhat.com/show_bug.cgi?id=2274719 and its clones Regarding RGW: see https://bugzilla.redhat.com/show_bug.cgi?id=2356355 and its clones Lou had written: > "something checking first for availability on 0.0.0.0:8080 as RGW is coming up before it actually binds to the network(s)" We hope to address this in RHCSv5 via https://bugzilla.redhat.com/show_bug.cgi?id=2356354
Adam King suggested we close this bug as a duplicate 2356355 *** This bug has been marked as a duplicate of bug 2356355 ***