when colocating the mgr dashboard module with other services it is essential to be able to configure the binding ip address because 8443 is frequently in use by ohter services this is supported in the dashboard module but can't be controlled via ceph-ansible [1] for deployments where the mgr module is deployed together with openstack, 8443 will be used by haproxy to forward requests correctly to the internal services 1. https://docs.ceph.com/docs/master/mgr/dashboard/#host-name-and-port
note that it's necessary to use a different server_addr per instance, hence the best approach is probably to use a key in this format: `advanced mgr/dashboard/##hostname##/server_addr`
@Giulio: currently, dashboard supports also localized `server_addr` (that is, cluster-wide setting or per-manager value). In fact, a localized setting (if existing) overrides the cluster-wide one. No need of code changes in dashboard.
(In reply to Ernesto Puerta from comment #2) > @Giulio: currently, dashboard supports also localized `server_addr` (that > is, cluster-wide setting or per-manager value). In fact, a localized setting > (if existing) overrides the cluster-wide one. No need of code changes in > dashboard. yeah the BZ is for ceph-ansible, to implement support for what is described in comment #1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:2231