Bug 2007648

Summary: Updated container images for 5.1
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sebastian Wagner <sewagner>
Component: BuildAssignee: Ken Dreyer (Red Hat) <kdreyer>
Status: CLOSED ERRATA QA Contact: Manasa <mgowri>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.1CC: gmeno, gsitlani, kdreyer, mgowri, pcuzner, sangadi
Target Milestone: ---   
Target Release: 5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-16.2.7-19.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-04 10:57:03 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: 2068135    

Description Sebastian Wagner 2021-09-24 13:25:48 UTC
For 5.1, we will need to add a few container images and I'd like to take this opportunity to streamline things a tiny bit. 

For 5.0, we have our base image and our own grafana image

    registry.redhat.io/rhceph/rhceph-5-rhel8:latest
    registry.redhat.io/rhceph/rhceph-5-dashboard-rhel8:latest

and some external monitoring images:

    registry.redhat.io/openshift4/ose-prometheus:v4.6
    registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.6
    registry.redhat.io/openshift4/ose-prometheus-alertmanager:v4.6

Does it make sense to keep those monitoring containers or is there a potential for an alignment with OCS? With cephadm, there is a possibility to also align on the entry point of those containers.

For 5.1, we will need two new downstream equivalents for upstream containers:

    docker.io/library/haproxy:2.3
    docker.io/arcts/keepalived
    prometheus-weebhook-snmp
 

As far as I can see, we already have those containers downstream already, but we'll need to become official stake holders of those container images in order to continue to get (security) updates.

Comment 1 RHEL Program Management 2021-09-24 13:25:55 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Sebastian Wagner 2021-09-30 09:58:47 UTC
This is a release blocker.

Comment 4 Ernesto Puerta 2021-10-08 17:49:21 UTC
*** Bug 1975742 has been marked as a duplicate of this bug. ***

Comment 8 Sebastian Wagner 2021-11-16 13:03:23 UTC
*** Bug 2023683 has been marked as a duplicate of this bug. ***

Comment 15 Ken Dreyer (Red Hat) 2021-12-17 15:45:14 UTC
I've opened https://github.com/red-hat-storage/cephci/issues/1002 to make sure we can override the haproxy image in cephci until we ship.

Comment 31 errata-xmlrpc 2022-04-04 10:57:03 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 (New container image for Red Hat Ceph Storage 5.1), 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-2022:1177

Comment 32 Red Hat Bugzilla 2023-09-15 01:15:30 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days