Bug 2384225 - [cephadm/build]Wrong image details in cephadm list-images output
Summary: [cephadm/build]Wrong image details in cephadm list-images output
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Build
Version: 8.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 8.1z2
Assignee: Justin Caratzas
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-29 12:07 UTC by Karun Josy
Modified: 2025-08-18 14:01 UTC (History)
3 users (show)

Fixed In Version: ibm-ceph-container-8-187
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-08-18 14:01:02 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-11847 0 None None None 2025-07-29 12:08:24 UTC
Red Hat Product Errata RHBA-2025:14015 0 None None None 2025-08-18 14:01:04 UTC

Description Karun Josy 2025-07-29 12:07:39 UTC
# Description of problem:

The installation of IBM 8.1z1 completes successfully; however, cephadm still displays image references pointing to the Red Hat registry. This appears to be a cosmetic issue, as the images are correctly mapped to the IBM registry in the Ceph configuration database. Shouldn't these be corrected as well?

========================
# cephadm list-images
[mgr]
mgr/cephadm/container_image_prometheus = registry.redhat.io/openshift4/ose-prometheus:v4.15
mgr/cephadm/container_image_loki = registry.redhat.io/openshift-logging/logging-loki-rhel8:v3.1.0
mgr/cephadm/container_image_promtail = registry.redhat.io/rhceph/rhceph-promtail-rhel9:v3.0.0
mgr/cephadm/container_image_node_exporter = registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.15
mgr/cephadm/container_image_alertmanager = registry.redhat.io/openshift4/ose-prometheus-alertmanager:v4.15
mgr/cephadm/container_image_grafana = registry.redhat.io/rhceph/grafana-rhel9:latest
mgr/cephadm/container_image_haproxy = registry.redhat.io/rhceph/rhceph-haproxy-rhel9:latest
mgr/cephadm/container_image_keepalived = registry.redhat.io/rhceph/keepalived-rhel9:latest
mgr/cephadm/container_image_nvmeof = registry.redhat.io/rhceph/ceph-nvmeof-rhel9:1.4
mgr/cephadm/container_image_snmp_gateway = registry.redhat.io/rhceph/snmp-notifier-rhel9:latest
mgr/cephadm/container_image_samba = cp.icr.io/cp/ibm-ceph/samba-server-rhel9:v8.1
mgr/cephadm/container_image_samba_metrics = cp.icr.io/cp/ibm-ceph/samba-metrics-rhel9:v8.1
mgr/cephadm/container_image_nginx = registry.redhat.io/rhel9/nginx-124:latest
mgr/cephadm/container_image_oauth2_proxy = registry.redhat.io/rhceph/oauth2-proxy-rhel9:v7.6.0


# podman images
REPOSITORY                                      TAG         IMAGE ID      CREATED      SIZE
cp.icr.io/cp/ibm-ceph/grafana-rhel9             latest      2bb22fadafdc  7 days ago   1.05 GB
cp.icr.io/cp/ibm-ceph/ceph-8-rhel9              latest      37978f52d069  8 days ago   1.19 GB
cp.icr.io/cp/ibm-ceph/prometheus                v4.15       894c5b3d83db  3 weeks ago  584 MB
cp.icr.io/cp/ibm-ceph/prometheus-node-exporter  v4.15       79ca1dd4c431  3 weeks ago  431 MB
cp.icr.io/cp/ibm-ceph/prometheus-alertmanager   v4.15       02d2258cb35b  3 weeks ago  468 MB


From ceph config database:

# ceph config get mgr mgr/cephadm/container_image_oauth2_proxy
cp.icr.io/cp/ibm-ceph/oauth2-proxy-rhel9:v7.6.0
# ceph config get mgr mgr/cephadm/container_image_alertmanager
cp.icr.io/cp/ibm-ceph/prometheus-alertmanager:v4.15
# ceph config get mgr mgr/cephadm/container_image_nvmeof
cp.icr.io/cp/ibm-ceph/nvmeof-rhel9:1.4
========================

# Version-Release number of selected component (if applicable):
IBM 8.1z1 
ceph version 19.2.1-222.el9cp (f2cd71cc2f7b46709c2351134ac89ea3e9f609b6)

# How reproducible:
Always

Comment 9 errata-xmlrpc 2025-08-18 14:01:02 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 (Red Hat Ceph Storage 8.1 security and bug fix 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/RHBA-2025:14015


Note You need to log in before you can comment on or make changes to this bug.