Bug 2167729
| Summary: | [Bluewash][Installation] Unable to deploy node-exporter daemon using ceph orchestrator | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Sayalee <saraut> |
| Component: | Build | Assignee: | Ken Dreyer (Red Hat) <kdreyer> |
| Status: | CLOSED NOTABUG | QA Contact: | Sayalee <saraut> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | cephqe-warriors, msaini, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 5.3z4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-07-25 06:43:05 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: | |||
|
Description
Sayalee
2023-02-07 11:51:59 UTC
The description has this command:
> ceph config set mgr mgr/cephadm/container_image_node_exporter cp.icr.io/cp/ibm-ceph/prometheus-node-exporter
When you do that, podman uses the ":latest" tag, rather than ":v4.10". We haven't pushed a floating latest tag IBM's registry for that image. We want users to use that v4.10 tag.
I've confirmed that cp.icr.io/cp/ibm-ceph/prometheus-node-exporter:v4.10 is properly set in the two files we ship in IBM Storage Ceph:
/usr/sbin/cephadm
/usr/share/ceph/mgr/cephadm/module.py
Are you still seeing errors when deploying or upgrading?
(In reply to Ken Dreyer (Red Hat) from comment #2) > The description has this command: > > > ceph config set mgr mgr/cephadm/container_image_node_exporter cp.icr.io/cp/ibm-ceph/prometheus-node-exporter > > When you do that, podman uses the ":latest" tag, rather than ":v4.10". We > haven't pushed a floating latest tag IBM's registry for that image. We want > users to use that v4.10 tag. > > I've confirmed that cp.icr.io/cp/ibm-ceph/prometheus-node-exporter:v4.10 is > properly set in the two files we ship in IBM Storage Ceph: > > /usr/sbin/cephadm > /usr/share/ceph/mgr/cephadm/module.py > > Are you still seeing errors when deploying or upgrading? Hello Ken, This issue is not observed with the latest IBM Ceph Storage 5.3z4/IBM Ceph Storage 6.1 deployments. Closing this bug. Thanks |