Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1528015

Summary: oc whomi returns forbidden - version of OC: 3.7.9
Product: OpenShift Container Platform Reporter: Markus Schreier <mschreie>
Component: ocAssignee: Juan Vallejo <jvallejo>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Mac OS   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-21 15:38:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***