Hide Forgot
Description of problem: When using the oauth flow in the jenkins image, after deleting a pipeline buildconfiguration from openshift, the user gets a read access permission denied error in the jenkins console and can no longer access the console. Upon logging out, the user is presented with the non-oauth login flow.
deleting a job in general based on jenkins log analysis seems to induced a bootup cycle of sorts in Jenkins (see InitReactorRunner.java in the jenkins core). aside from deleting the bc, i was able to log into jenkins and manually delete the sample-pipeline job and achieve the same effect. This bootup cycle has the effect of resetting the system to the standard jenkins login (overriding our dynamic override of the login provider to oauth). I'll need to either using the existing listeners / filters already in play, or also use the plug points that sync plugin uses, to learn of this job deleting and re-institute.
the jenkins-*-centos7 images have been updated with v0.3 of the openshift-login plugin, which has the fix for this bug, and pushed to docker.io
Verified docker.io/openshift/jenkins-1-centos7 5b7b34dd4518 openshift-login 0.3 openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0