Closed adrianriobo closed 4 weeks ago
I tried it on my system and got similar issue, also not able to pull image using podman
$ sudo podman pull --authfile /var/lib/kubelet/config.json registry.redhat.io/redhat/community-operator-index:v4.17
Trying to pull registry.redhat.io/redhat/community-operator-index:v4.17...
WARN[0060] Failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/redhat/community-operator-index:v4.17: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 104.114.107.26:443: i/o timeout
WARN[0121] Failed, retrying in 1s ... (2/3). Error: initializing source docker://registry.redhat.io/redhat/community-operator-index:v4.17: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 104.114.107.26:443: i/o timeout
WARN[0182] Failed, retrying in 1s ... (3/3). Error: initializing source docker://registry.redhat.io/redhat/community-operator-index:v4.17: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 104.114.107.26:443: i/o timeout
Error: initializing source docker://registry.redhat.io/redhat/community-operator-index:v4.17: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 104.114.107.26:443: i/o timeout
But then I created a instance on GCP and tried with same bundle where I don't see this issue
$ oc get co
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
authentication 4.17.1 True False False 28m
config-operator 4.17.1 True False False 2d22h
console 4.17.1 True False False 29m
control-plane-machine-set 4.17.1 True False False 2d22h
dns 4.17.1 True False False 29m
etcd 4.17.1 True False False 2d22h
image-registry 4.17.1 True False False 29m
ingress 4.17.1 True False False 2d22h
kube-apiserver 4.17.1 True False False 2d22h
kube-controller-manager 4.17.1 True False False 2d22h
kube-scheduler 4.17.1 True False False 2d21h
kube-storage-version-migrator 4.17.1 True False False 29m
machine-api 4.17.1 True False False 2d22h
machine-approver 4.17.1 True False False 2d22h
machine-config 4.17.1 True False False 2d22h
marketplace 4.17.1 True False False 2d22h
network 4.17.1 True False False 2d22h
openshift-apiserver 4.17.1 True False False 29m
openshift-controller-manager 4.17.1 True False False 19m
openshift-samples 4.17.1 True False False 2d22h
operator-lifecycle-manager 4.17.1 True False False 2d22h
operator-lifecycle-manager-catalog 4.17.1 True False False 2d22h
operator-lifecycle-manager-packageserver 4.17.1 True False False 29m
service-ca 4.17.1 True False False 2d22h
$ oc get pods -n openshift-marketplace
NAME READY STATUS RESTARTS AGE
certified-operators-2tzwb 1/1 Running 0 29m
community-operators-cz89w 1/1 Running 0 29m
marketplace-operator-99df5f478-csgh2 1/1 Running 0 30m
redhat-marketplace-v8pxp 1/1 Running 0 29m
redhat-operators-rhv68 1/1 Running 0 29m
Tested today and there is no timeout / auth issues, so I will close the issue as it seemed a random/temporary issue. Related with the registry.redhat.io and not with the bundle itself.
Testing bundles for OCP 4.17.1 we see errors while trying to pull images for marketplace and monitoring operators:
It can be seeing on all platforms