Description of problem: Now in 4.0 jenkins-agent-nodejs-8-rhel7 and jenkins-agent-maven-35-rhel7 are using openshift3 project, should use openshift project Version-Release number of selected component (if applicable): jenkins-agent-maven-35-rhel7 v4.0 3bba1b953a1f jenkins-agent-nodejs-8-rhel7 v4.0 8633d5d950b8 How reproducible: always Steps to Reproduce: 1.https://github.com/openshift/jenkins/blob/master/2/contrib/jenkins/kube-slave-common.sh#L27 should change openshift3 to be openshift https://github.com/openshift/jenkins/blob/master/2/contrib/jenkins/kube-slave-common.sh#L28 should change openshift3 to be openshift 2. 3. Actual results: jenkins slave use openshift3 project Expected results: should use openshift project Additional info:
FYI, if https://github.com/openshift/jenkins/blob/master/openshift/imagestreams/jenkins-rhel7-ppc64le.json#L41 need update too?
> FYI, if https://github.com/openshift/jenkins/blob/master/openshift/imagestreams/jenkins-rhel7-ppc64le.json#L41 need update too? yeah, should be.
Ben - do you *think* enough pieces of our various openshift/release and ART related activities have occurred such that we can mark this done? Or do you want to gate this one on when the samples operator change drops to tag the jenkins payload images into the jenkins imagestream? Also, we could probably make an argument that https://jira.coreos.com/browse/DEVEXP-202 should be used to track this space vs. this bugzilla, no? thanks
Let's hold this open until all the payload related changes are in place. Strictly speaking it's probably a bit redundant, but it'd be good to get explicit QE verification of the slave configuration working correctly once it is switched to use the payload.
fyi PR https://github.com/openshift/cluster-samples-operator/pull/81 is the last piece of the half dozen or so changes wrt getting the jenkins images into the 4.0 payload and tweaking various reference in CI and image startup to leverage those image ref Specifically wrt the kube-slave-common.sh config, those image refs in the sample maven/nodejs pod template configs will be openshift cluster image registry refs.
PR marked for merge
OK with PR https://github.com/openshift/jenkins/pull/775 merging we are done here Our agent pod template examples will set up the image as a pull spec to the internal registry which actually leverages new imagestreams for the two agent images, where those imagestreams are populated via the release payload
Default to use image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-maven:latest and image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-nodejs:latest in jenkins server. $ oc get is -n openshift | grep jenkins jenkins image-registry.openshift-image-registry.svc:5000/openshift/jenkins 2,latest 42 minutes ago jenkins-agent-maven image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-maven latest,v4.0 42 minutes ago jenkins-agent-nodejs image-registry.openshift-image-registry.svc:5000/openshift/jenkins-agent-nodejs latest,v4.0 42 minutes ago $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-13-204401 True False 36m Cluster version is 4.0.0-0.nightly-2019-02-13-204401
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-2019:0758