Hide Forgot
Description of problem: Repo openshift/service-serving-cert-signer has renamed to openshift/service-ca-operator for a while, but the openshift-service-cert-signer image still build from a obsolete repo Version-Release number of selected component (if applicable): $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-04-234414 True False 172m Cluster version is 4.0.0-0.nightly-2019-03-04-234414 How reproducible: # TAG_ID=2019-03-04-234414 # oc adm release info --pullspecs registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-${TAG_ID} | grep service-serving service-serving-cert-signer quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:032cf8f0fd7ac91f58ee670244892812cd024d8d7eee923266b9acf97ee21ac4 # oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:032cf8f0fd7ac91f58ee670244892812cd024d8d7eee923266b9acf97ee21ac4 Name: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:032cf8f0fd7ac91f58ee670244892812cd024d8d7eee923266b9acf97ee21ac4 ... io.k8s.description=This is the base image from which all OpenShift Container Platform images inherit. io.k8s.display-name=OpenShift Container Platform RHEL 7 Base io.openshift.build.commit.id=309242162ed5bcf9398fca0ba9418244ec7c6808 io.openshift.build.commit.url=https://github.com/openshift/service-serving-cert-signer/commit/309242162ed5bcf9398fca0ba9418244ec7c6808 io.openshift.build.source-location=https://github.com/openshift/service-serving-cert-signer ... Actual results: Expected results: Additional info:
The issue should be fixed now, build repo point to the right one. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-18-223058 True False 23h Cluster version is 4.0.0-0.nightly-2019-03-18-223058
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758