Red Hat Bugzilla – Bug 1390865
Pipeline stages display abnormally on web console
Last modified: 2017-03-08 13:43 EST
Created attachment 1216372 [details] pipeline.gif Description of problem: Create jenkinsPipelineStrategy bc and deploy jenkins master pod. Start pipeline build, check stage on build page and overview page, the stages status is unstable, they flash quickly, sometimes stage 2 status would cover stage 1 status. Version-Release number of selected component (if applicable): openshift v3.4.0.18+ada983f kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 image info: $ docker images | grep jenkins # on pod's node registry.ops.openshift.com/openshift3/jenkins-1-rhel7 <none> 2552a065d61d 13 hours ago 679.7 MB How reproducible: Always Steps to Reproduce: 1.Create jenkinsPipelineStrategy bc, deploy jenkins master pod and edit bc to add stages. $ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json $ oc edit bc sample-pipeline # Edit as follows by adding lines 'input message' into stages: ... jenkinsfile: |- node('nodejs') { stage 'stage1' input message: 'really approve?' stage 'stage2' input message: 'really approve?' …… ) 2.Start a build $ oc start-build sample-pipeline 3.Wait a moment for the build to be running, check the pipeline build in bc page and overview page on web console: Actual results: 3.The stages status is unstable, they flash quickly, sometimes stage 2 status would cover stage 1 status. Refer to attachment. Expected results: 3.Every stage should go smoothly and display well on bc and overview page. Additional info:
yanpzhan@redhat.com can you check if there were two jobs started in the Jenkins console for this build? I suspect two Jenkins jobs are trying to sync status back to the same OpenShift build, causing the flicker you're seeing. Also please attach the log for the Jenkins pod to see if there are any errors.
Checked again. Indeed as you said: after I approved stage 1, two jenkins jobs are running on jenkins console which causing the flicker, and after a while 3 jenkins jobs showing on jenkins console, but I didn't start andy jenkins job manually. Could see that nodejs pod number increased: # oc get pod NAME READY STATUS RESTARTS AGE jenkins-1-bthzs 1/1 Running 0 21m mongodb-1-mqzhs 1/1 Running 0 21m nodejs-5f0f2217a1c5 1/1 Running 0 2m # oc get pod NAME READY STATUS RESTARTS AGE jenkins-1-bthzs 1/1 Running 0 25m mongodb-1-mqzhs 1/1 Running 0 25m nodejs-5f0f2217a1c5 1/1 Running 0 6m nodejs-5f31e6fcbc56 1/1 Running 0 4m # oc get pod NAME READY STATUS RESTARTS AGE jenkins-1-bthzs 1/1 Running 0 31m mongodb-1-mqzhs 1/1 Running 0 31m nodejs-5f0f2217a1c5 1/1 Running 0 12m nodejs-5f31e6fcbc56 1/1 Running 0 9m nodejs-5f8f0d1b0074 1/1 Running 0 3m Attach jenkins log.
Created attachment 1217301 [details] jenkins-jobs
Created attachment 1217302 [details] jenkinslog
This appears to be a sync pipeline issue. Assigning to Jimmi. Jimmi, let us know if there is anything we can do to help.
Please try with latest Jenkins image - cannot reproduce with that, console runs smoothly for me.
Tested on OCP v3.4.0.26 with latest jenkins images: # docker images|grep jenkins registry.ops.openshift.com/openshift3/jenkins-2-rhel7 <none> d126876bf60a 2 days ago 677.4 MB Now the pipeline stages show well on web console, the issue is fixed, so move the bug to Verified.
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-2017:0066