Thanks Francesco for the analysis. I proposed a patch to deploy prometheus and alertmanager on the storage network.
how to test: Deply ceph with dashboard enabled and then check if - ceph dashboard prometheus config ( #ceph dashboard get-prometheus-api-host ) should match with ceph_promethus config in haproxy (/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg ) - prometheus and alert_manager vip is tied to storage network - ceph dashboard shouln't report any error saying 'unable to reach prometheus endpoint'
Hi Gareth, The workaround mentioned in the doc text has ip details which will not be same for all environments. I feel it is better to get rid of the workaround details in doc text (as we have the fix already) and keep it simple. wdyt ? Regards, Manoj Katari
yeah, this fix is not part of the latest compose and the target milestone is set to z4 already.
Hi Greg, Bug is fixed and targeted for z4, @alfrgarc can comment on verification part. In z4 release notes, i agree that it should be a 'Bug fix' rather than a 'known issue'.
Hi Greg, Proposed Doc text works for me.
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 (RHOSP 17.1.4 bug fix and enhancement 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/RHBA-2024:9974