OpenShift is not able to roll out deployments because it fails to pull openshift3/ose-deployer:v3.11.141 image from registry.redhat.io due to invalid certificate (certificate is valid for *.vzeesp.com, vzeesp.com, not registry.redhat.io).
openshift3/ose-deployer:v3.11.141
registry.redhat.io
Reproducer:
[root@os-master01 ~][PROD]# oc -n koschei describe pod/repo-resolver-2-deploy
Output:
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 8m default-scheduler Successfully assigned koschei/repo-resolver-2-deploy to os-node01.phx2.fedoraproject.org Normal Pulling 7m (x4 over 8m) kubelet, os-node01.phx2.fedoraproject.org pulling image "registry.redhat.io/openshift3/ose-deployer:v3.11.141" Warning Failed 7m (x4 over 8m) kubelet, os-node01.phx2.fedoraproject.org Failed to pull image "registry.redhat.io/openshift3/ose-deployer:v3.11.141": rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.redhat.io/v2/: x509: certificate is valid for *.vzeesp.com, vzeesp.com, not registry.redhat.io Warning Failed 7m (x4 over 8m) kubelet, os-node01.phx2.fedoraproject.org Error: ErrImagePull Warning Failed 6m (x7 over 8m) kubelet, os-node01.phx2.fedoraproject.org Error: ImagePullBackOff Normal BackOff 3m (x20 over 8m) kubelet, os-node01.phx2.fedoraproject.org Back-off pulling image "registry.redhat.io/openshift3/ose-deployer:v3.11.141"
Fixed by @kevin in commit 1269412
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
ugh... we keep getting bit by this!
Login to comment on this ticket.