Bug 2315072
| Summary: | Deploying prometheus service for the first time, will not update PROMETHEUS_API_HOST url under manager module. | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Chaithra <ckulal> | |
| Component: | Cephadm | Assignee: | Shweta Bhosale <shbhosal> | |
| Status: | CLOSED ERRATA | QA Contact: | Chaithra <ckulal> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.0 | CC: | adking, cephqe-warriors, kdeb, rpollack, shbhosal, tserlin | |
| Target Milestone: | --- | Flags: | ckulal:
needinfo+
|
|
| Target Release: | 8.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ceph-19.2.1-86.el9cp | Doc Type: | Bug Fix | |
| Doc Text: |
.`PROMETHEUS_API_HOST` gets set during Cephadm Prometheus deployment
Previously, `PROMETHEUS_API_HOST` would not always get set when Cephadm initially deployed Prometheus. This issue was seen most commonly when bootstrapping a cluster with `--skip-monitoring-stack`, then deploying Prometheus at a later time. As a result monitoring information could be unavailable.
With this fix, `PROMETHEUS_API_HOST` gets set during Cephadm Prometheus deployment and monitoring information is available, as expected.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2351203 (view as bug list) | Environment: | ||
| Last Closed: | 2025-06-26 12:16:44 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2351203, 2351689 | |||
|
Description
Chaithra
2024-09-27 04:28:35 UTC
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 (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), 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-2025:9775 |