[jboss-jira] [JBoss JIRA] (SWSQE-106) Modify Jenkins service user to permit it to create projects

Filip Brychta (JIRA) issues at jboss.org
Thu Mar 29 13:45:00 EDT 2018


    [ https://issues.jboss.org/browse/SWSQE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554342#comment-13554342 ] 

Filip Brychta commented on SWSQE-106:
-------------------------------------

Configured mvn slaves that following commands pass:
mvn --version
oc whoami
oc new-project fbr-testik
oc project fbr-testik
oc status
oc new-app mysql

> Modify Jenkins service user to permit it to create projects
> -----------------------------------------------------------
>
>                 Key: SWSQE-106
>                 URL: https://issues.jboss.org/browse/SWSQE-106
>             Project: Swift Sunshine QE
>          Issue Type: QE Task
>            Reporter: Kevin Earls
>            Assignee: Filip Brychta
>            Priority: Minor
>
> While trying to run a simple Jenkins job from http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com/ the command "sh new-project kearls-temp0' gave me:
>     oc new-project kearls-temp0 .  
>     Error from server (Forbidden): You may not request a new project via this API.
> You need to do the following to permit the jenkins service account to create projects:
>     oc login -u system:admin 
>     oc adm policy add-cluster-role-to-user self-provisioner -z jenkins -n myproject
>     oc create -f jenkins-ci/clusterpolicy.json
>     oc policy add-cluster-role-to-user create_project_role system:serviceaccount:myproject:jenkins
> Substitute the actual Jenkins project name for 'myproject'. More information is available here: https://access.redhat.com/solutions/2988521 and https://github.com/openshift/origin/issues/17678
> You can find a copy of clusterpolicy.json described in the access.redhat.com link or here:  https://github.com/kevinearls/jaeger-openshift/blob/kiali-337/jenkins-ci/clusterpolicy.json
> I don't know if this will require a Jenkins or OS cluster restart.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list