Hide Forgot
cluster-reader is what I can use to see a cluster. Since global config CR and config maps are not secret nor escalating, I should either be able to view them, or view a subset of them.
PR: https://github.com/openshift/origin/pull/22533
*** Bug 1698819 has been marked as a duplicate of this bug. ***
Updated PR: https://github.com/openshift/cluster-config-operator/pull/47 Closed the previously posted PR.
https://github.com/openshift/cluster-config-operator/pull/47 merged with the `system:openshift:cluster-config-operator:cluster-reader` cluster role.
The 4.1.0-0.nightly-2019-04-23-223857 not include this fix. $ oc adm release info --pullspecs registry.svc.ci.openshift.org/ocp/release:4.1.0-0.nightly-2019-04-23-223857 | grep cluster-config-operator cluster-config-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:265689fce27a37057f1dbec76764a6c4d659d3fc3e542e499e2918fab1ba47b7 $ oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:265689fce27a37057f1dbec76764a6c4d659d3fc3e542e499e2918fab1ba47b7 | grep -A 6 commit.id io.openshift.build.commit.id=f53033e30ed457046b1b77f8259e99d5b3b55f2e io.openshift.build.commit.url=https://github.com/openshift/cluster-config-operator/commit/f53033e30ed457046b1b77f8259e99d5b3b55f2e io.openshift.build.source-location=https://github.com/openshift/cluster-config-operator io.openshift.release.operator=true io.openshift.tags=openshift,base name=openshift/ose-cluster-config-operator release=201904211700
There was an issue with image promotions yesterday. I verified that this is working in https://origin-release.svc.ci.openshift.org/releasestream/4.1.0-0.okd/release/4.1.0-0.okd-2019-04-24-182549.
Verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-04-25-002910 True False 5h22m Cluster version is 4.1.0-0.nightly-2019-04-25-002910
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