Testing of rhel based image payloads started this past weekend. That rhel based image payload content requires the coreos pull secret. Our recent change to provide the jenkins images via the payload hence not required credentials irrespective of our other rhel images samples still pointing to registry.access.redhat.com (where we are waiting for the SD team to provide TBR credentials in the install) So we accelerated the move to having credentials out of the box. Specifically: - the PR for this copies the coreos pull secret to the openshift namespace - we now monitor the kube-system namespace for changes to the coreos-pull-secret - we no longer monitor the operator namespace for secrets - we updated the directions in the readme accordingly QE will (once again) have to tweak their test cases accordingly.
PR https://github.com/openshift/cluster-samples-operator/pull/99 is up
PR has merged
coreos-pull-secret under kube-system ns could be synced to samples-registry-credentials secret under openshift project. $oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-13-204401 True False 93m Cluster version is 4.0.0-0.nightly-2019-02-13-204401
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