-
Bug
-
Resolution: Done
-
Blocker
-
1.10.0
-
None
-
None
-
False
-
None
-
False
-
-
Description of problem:
1.10 RC installation fails on disconnected installation as kubeproxy image was not included in the RC
Workaround
None identified and as this would effect the customers, we need a new RC with kubeproxy image
Prerequisites (if any, like setup, operators/versions):
1.10 RC
Steps to Reproduce
- Spin up a disconnected cluster
- Create a catalog source with new image
- Install the operator
Actual results:
Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:da5d5061dbc2ec5082cf14b6c600fb5400b83cf91d7ccebfa80680a238d275db": rpc error: code = Unknown desc = (Mirrors also failed: [ec2-3-139-67-102.us-east-2.compute.amazonaws.com:5000/devtools_gitops/openshift4-ose-kube-rbac-proxy@sha256:da5d5061dbc2ec5082cf14b6c600fb5400b83cf91d7ccebfa80680a238d275db: reading manifest sha256:da5d5061dbc2ec5082cf14b6c600fb5400b83cf91d7ccebfa80680a238d275db in ec2-3-139-67-102.us-east-2.compute.amazonaws.com:5000/devtools_gitops/openshift4-ose-kube-rbac-proxy: manifest unknown]): registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:da5d5061dbc2ec5082cf14b6c600fb5400b83cf91d7ccebfa80680a238d275db: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": Forbidden
Expected results:
Installation is successful
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- is cloned by
-
-
- Closed
-