Red Hat Bugzilla – Bug 1573558
Error message for sub resources is wrong
Last modified: 2018-10-11 03:19:39 EDT
Got rejected accessing build logs in a namespace directly via the API error: Unable to retrieve logs from failed build: builds.build.openshift.io "src" is forbidden: User "smarterclayton" cannot get builds.build.openshift.io/logs in the namespace "test-ci-op": User "smarterclayton" cannot get builds/logs.build.openshift.io in project "test-ci-op" We display the same subresource message in two different ways. I also don't know why we show the error twice (shouldn't be nested). Might be a build team problem.
Known issue: https://github.com/openshift/origin/issues/15828
Also Error from server (Forbidden): namespaces "ci-op-b11b8c1ba3" is forbidden: User "smarterclayton" cannot delete namespaces in the namespace "ci-op-b11b8c1ba3": User "smarterclayton" cannot delete namespaces in project "ci-op-b11b8c1ba3" Duplicate plus "cannot delete namespaces in the namespace" makes me die a bit on the inside.
https://github.com/openshift/origin/pull/20379
Clayton, a fix for this issue is available in the PR mentioned in #comment3 If you think this is 3.11 material please approve the PR, otherwise I'll shelve it for the following release and change this bugzilla target.
Merged to master: https://github.com/openshift/origin/pull/20379
Verified. # openshift version openshift v3.11.0-0.22.0 # oc get bc -n install-test No resources found. Error from server (Forbidden): buildconfigs.build.openshift.io is forbidden: User "aa" cannot list buildconfigs.build.openshift.io in the namespace "install-test": no RBAC policy matched # oc delete ns default Error from server (Forbidden): namespaces "default" is forbidden: User "aa" cannot delete namespaces in the namespace "default": no RBAC policy matched
# oc get --raw /apis/build.openshift.io/v1/namespaces/aa/builds/ruby-ex-1/log Error from server (Forbidden): builds.build.openshift.io "ruby-ex-1" is forbidden: User "system:anonymous" cannot get builds.build.openshift.io/log in the namespace "aa": no RBAC policy matched
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-2018:2652