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

Bug 1339507

Summary:	"oadm policy" checks nothing on the existense of the user/group being manipulated
Product:	OpenShift Container Platform	Reporter:	Xia Zhao <xiazhao>
Component:	apiserver-auth	Assignee:	Jordan Liggitt <jliggitt>
Status:	CLOSED DUPLICATE	QA Contact:	weiwei jiang <wjiang>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aos-bugs, mmccomas, wsun
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-31 13:52:06 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 Xia Zhao 2016-05-25 08:22:16 UTC

Problem description: 
Attempt to manipulate a non-existed user/group through "oadm policy", the following commands can complete without any error returned: 
# oadm policy add-cluster-role-to-user cluster-admin system:serviceaccount:non-exist:non-exist
# oadm policy add-role-to-user cluster-admin system:serviceaccount:non-exist:non-exist
# oadm policy add-role-to-user cluster-admin non-exist
# oadm policy add-role-to-group cluster-admin non-exist
# oadm policy add-cluster-role-to-group cluster-admin system:serviceaccount:non-exist:non-exist

Version-Release number of selected component (if applicable):
oc v1.3.0-alpha.0-667-g2f54fb7
kubernetes v1.3.0-alpha.1-331-g0522e63

How reproducible:
Always

Steps to Reproduce:
1. As described in "Problem description"

Actual Result:
"oadm policy" checks nothing on the existense of the user/group being manipulated

Expected Result:
"oadm policy" should check on the existense of the user/group being manipulated, and give error msg if needed

Additional info:

Comment 1 Jordan Liggitt 2016-05-31 13:52:06 UTC


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