-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.8
-
Critical
-
None
-
Rejected
-
All
-
If docs needed, set a value
Description of problem:
After installing the Red Hat OpenShift Gitops Operator Version 1.4.4 on a OpenShift Cluster Version 4.8.31 (Kubernetes v.1.21.6+b82a451) it is not possible to create an ArgoCD instance. The PODs run into error:
Pulling image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8"
Warning Failed 12s (x4 over 105s) kubelet, 10.13.184.98 Failed to pull image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8": rpc error: code = Unknown desc = Error reading manifest sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8 in registry.redhat.io/openshift-gitops-1/argocd-rhel8: StatusCode: 404, <HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>
An e...
Version-Release number of selected component (if applicable):
Red Hat OpenShift Gitops Operator Version 1.4.4
OpenShift Cluster Version 4.8.31
Kubernetes v.1.21.6+b82a451
How reproducible:
Install Red Hat OpenShift Gitops Operator over OperatorHub, then Create a new ArgoCD instance.
Steps to Reproduce:
1. Login to Cluster
2. Install Red Hat OpenShift Gitops Operator vie OperatorHub
3. Create a new ArgoCD Instance
Actual results:
ArgoCD PODs from new Instance will fail to start while pulling the Image from red hat registry.
Pulling image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8"
Warning Failed 12s (x4 over 105s) kubelet, 10.13.184.98 Failed to pull image "registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8": rpc error: code = Unknown desc = Error reading manifest sha256:ff4ad30752cf0d321cd6c2c6fd4490b716607ea2960558347440f2f370a586a8 in registry.redhat.io/openshift-gitops-1/argocd-rhel8: StatusCode: 404, <HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>
An e...
Expected results:
PODs come up as expected without errors.
Additional info:
This seems to be a general issue, since many other people are having the same behaviour after updating the Operator or installing it first time on a cluster.
