Bug 1371434

Summary:	Error appears when creating resource(s) in openshift via jenkins
Product:	OpenShift Container Platform	Reporter:	wewang <wewang>
Component:	ImageStreams	Assignee:	Ben Parees <bparees>
Status:	CLOSED ERRATA	QA Contact:	Wang Haoran <haowang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	aos-bugs, jokerman, mmccomas, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-27 09:46:53 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:

Comment 1 Ben Parees 2016-08-30 13:05:50 UTC

The jenkins pod is run using serviceaccount "jenkins" now, not "default", so you need to add the permissions to system:serviceaccount:test:jenkins

note that those permissions are automatically added to the jenkins service account for the project in which you created the jenkins server, so you only need to add them for project "test1" in your scenario.

see:
https://github.com/openshift/origin/blob/master/examples/jenkins/jenkins-ephemeral-template.json#L153-L175

Comment 2 wewang 2016-08-31 02:14:14 UTC

updated cases, and verified when using system:serviceaccount:test:jenkins, thanks@Ben Parees

Comment 3 wewang 2016-08-31 02:20:28 UTC

pls also update docs:https://github.com/openshift/origin/blob/master/examples/jenkins/README.md, it seems still using default ,thx

Comment 4 Ben Parees 2016-08-31 02:47:56 UTC

Sure, readme is updated here:
https://github.com/openshift/origin/pull/10725

notice that i removed the step entirely as it is not necessary when using the new template since the new template creates the service account and adds the edit permission.  For your scenario (accessing a secondary project) you'll still need to add the edit permission to the appropriate service account.

Comment 6 errata-xmlrpc 2016-09-27 09:46:53 UTC

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-2016:1933