-
Bug
-
Resolution: Unresolved
-
Blocker
-
1.1.0
-
None
-
None
-
False
-
-
False
-
-
-
None
Version of components:
COO 1.1.0
OCP 4.12
COO Index image:
quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator/coo-fbc-v4-12@sha256:f4ccb204c8bb0f73b6c7af3c7c7965cd84b58d10e6387431904b8fe0ab5408bc
Description of the issue:
When COO 1.1.0 operator is deployed, the Perses operator pod fails to start due to image pull issue. Following is the error in the Perses operator deployment.
Warning Failed 26s (x2 over 42s) kubelet Failed to pull image "registry.redhat.io/cluster-observability-operator/perses-operator-0-1-rhel9@sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab": rpc error: code = Unknown desc = (Mirrors also failed: [quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator/perses-operator-0-1-rhel9@sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab: reading manifest sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab in quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator/perses-operator-0-1-rhel9: unauthorized: access to the requested resource is not authorized]): registry.redhat.io/cluster-observability-operator/perses-operator-0-1-rhel9@sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab: reading manifest sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab in registry.redhat.io/cluster-observability-operator/perses-operator-0-1-rhel9: unauthorized: access to the requested resource is not authorized
The image referenced by operator deployment is:
registry.redhat.io/cluster-observability-operator/perses-operator-0-1-rhel9@sha256:53dfd71368c5105b8069331c2f73158f214c4c4934c0d652eb2ae3462c47d5ab
While the one we have in quay has repo
redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator/perses-0-1-rhel9-operator
