Bug 1528015 - oc whomi returns forbidden - version of OC: 3.7.9
Summary: oc whomi returns forbidden - version of OC: 3.7.9
Keywords:
Status: CLOSED DUPLICATE of bug 1528016
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.7.0
Hardware: Unspecified
OS: Mac OS
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Juan Vallejo
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-20 18:56 UTC by Markus Schreier
Modified: 2017-12-21 15:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-21 15:38:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Markus Schreier 2017-12-20 18:56:42 UTC
Description of problem:
current version of oc shows an error:
$ oc-3.7.9 whoami
Error from server (Forbidden): User "developer" cannot get user.openshift.io.users at the cluster scope

Version-Release number of selected component (if applicable):
Markuss-MacBook-Pro:ansible mschreie$ oc-3.7.9 version
oc v3.7.9
kubernetes v1.7.6+a08f5eeb62
features: Basic-Auth

Server https://openshift.hailstorm2.coe.muc.redhat.com:443
openshift v3.5.5.31
kubernetes v1.5.2+43a9be4


How reproducible:
oc login
user: admin
oc whoami
-> error

Doing the same with older version of oc works, e.g.:
oc version
oc v3.6.173.0.83
kubernetes v1.6.1+5115d708d7
features: Basic-Auth

Server https://openshift.hailstorm2.coe.muc.redhat.com:443
openshift v3.5.5.31
kubernetes v1.5.2+43a9be4



Actual results:
Error from server (Forbidden): User "developer" cannot get user.openshift.io.users at the cluster scope


Expected results:
admin

Additional info:
colleague is having same issue on RHEL as I have on MAC when connecting against the same OpenShift installation.

Comment 1 Juan Vallejo 2017-12-21 15:38:02 UTC

*** This bug has been marked as a duplicate of bug 1528016 ***


Note You need to log in before you can comment on or make changes to this bug.