Bug 2251176
| Summary: | [RHOSP 17.1] Ceph dashboard looks for endpoints that are not available in haproxy config. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Luca Davidde <ldavidde> |
| Component: | tripleo-ansible | Assignee: | Manoj Katari <mkatari> |
| Status: | CLOSED ERRATA | QA Contact: | Alfredo <alfrgarc> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 17.1 (Wallaby) | CC: | alfrgarc, astupnik, fpantano, gregraka, jelynch, johfulto, mariel, mkatari, pgrist |
| Target Milestone: | z4 | Keywords: | Triaged |
| Target Release: | 17.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tripleo-ansible-3.3.1-17.1.20231201170809.8debef3.el9ost | Doc Type: | Bug Fix |
| Doc Text: |
Before this update, the Ceph Dashboard could not reach the Prometheus service endpoint and displayed the following error message: `404 not found.` This error occurred because the configuration of the VIP for the Prometheus service was not correct. In RHOSP 17.1.4, this problem has been resolved and the Dashboard is now able to reach the Prometheus service endpoint.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-11-21 09:39:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 16
Manoj Katari
2023-11-28 13:14:52 UTC
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 |