Bug 1917703

Summary: [Logging 5.0] use catalog image name in CSV
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: Vimal Kumar <vimalkum>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: high    
Version: 4.7CC: aos-bugs, jcantril, periklis
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 11:22:33 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 Anping Li 2021-01-19 08:19:24 UTC
Description of problem:
The namespace is still openshift4 in CSV. To release logging 5.0, we must update all logging images namespace to openshift-logging.


Version-Release number of selected component (if applicable):
5.0

How reproducible:
Always

Steps to Reproduce:
1. check the packagemanifests for cluster logging 5.0

oc get packagemanifests cluster-logging -o json |grep relatedImages -A 5
                    "relatedImages": [
                        "registry.redhat.io/openshift4/ose-cluster-logging-operator@sha256:08c68e54afa5f312a9d7072a5fbc96b87cf47ab39200a4cd75f5262d72ba7b80",
                        "registry.redhat.io/openshift4/ose-logging-curator5@sha256:6861b756c45a5e96e17b18c837f2cf6c7e2a1b0273447f7a6eb13c34d0d2ba61",
                        "registry.redhat.io/openshift4/ose-logging-fluentd@sha256:b5932ad71a4c226f9d15e6512c2d5456338bfe49deb48b6ff9df34366e380f5b"
                    ],
                    "version": "5.0.0-6"
$ oc get packagemanifests elasticsearch-operator -o json |grep relatedImages -A 6
                    "relatedImages": [
                        "registry.redhat.io/openshift4/ose-oauth-proxy@sha256:625709e0f8d15024730894c3d875451cbda35d58b7082ab2adf6813a637cf7b6",
                        "registry.redhat.io/openshift4/ose-elasticsearch-proxy@sha256:90c8957494881e81b9955aed75e0cd31420582811f2d223911f9a0c1b1e15ea5",
                        "registry.redhat.io/openshift4/ose-elasticsearch-operator@sha256:6c7fba8cc3e12b82ff264cf472f515b3101839fb1ceeef2492f1a67fd084bc37",
                        "registry.redhat.io/openshift4/ose-logging-elasticsearch6@sha256:18545ea2b97a744e0cb22bfa98be24f114022d6c2cb91be6cbebc2c37754eb3b",
                        "registry.redhat.io/openshift4/ose-logging-kibana6@sha256:a91141d9a42864691fb4fab8f2fb6a67450ad7c46b0affea476d14990bfbbdf7"
                    ],
Actual results:
The pull spec is registry.redhat.io/openshift4/.

Expected results:
The pull spec is registry.redhat.io/openshift-logging/

Additional info:
1) The pull-spec in brew should be registry-proxy.engineering.redhat.com/rh-osbs/openshift-logging-
2) The exception is registry.redhat.io/openshift4/ose-oauth-prox which should keep the namespace openshift4.

Comment 1 Anping Li 2021-01-19 13:06:31 UTC
If the CSV are correctly after the packages are pushed to stage. we can downgrade the Severity.

Comment 3 Anping Li 2021-01-27 01:24:36 UTC
Verified on cluster-logging.5.0.0-29,elasticsearch-operator.5.0.0-32

Comment 4 Vimal Kumar 2021-01-27 08:07:14 UTC
Moving to ON_QA

Comment 7 errata-xmlrpc 2021-02-24 11:22:33 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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652