Bug 1397284

Summary: Jenkins pod cannot be ready
Product: OpenShift Container Platform Reporter: Dongbo Yan <dyan>
Component: ImageStreamsAssignee: Troy Dawson <tdawson>
Status: CLOSED CURRENTRELEASE QA Contact: Wang Haoran <haowang>
Severity: high Docs Contact:
Priority: high    
Version: 3.4.0CC: aos-bugs, bparees, jokerman, mmccomas, tdawson
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-23 14:21:01 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:
Attachments:
Description Flags
Jenkins pod log none

Description Dongbo Yan 2016-11-22 07:29:37 UTC
Created attachment 1222605 [details]
Jenkins pod log

Description of problem:
Jenkins pod cannot be ready with jenkins-1-rhel7 and jenkins-2-rhel7 image

Version-Release number of selected component (if applicable):
brew-pulp.../openshift3/jenkins-1-rhel7      df4eb0c5f3ab  
brew-pulp.../openshift3/jenkins-2-rhel7      65ea34c5317f  

openshift v3.4.0.28+dfe3a66
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

How reproducible:
Always

Steps to Reproduce:
1.Create a project
2.Create a jenkins server
 $oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/jenkins-ephemeral-template.json
3.Check jenkins pod status, and jenkins pod log

Actual results:
Jenkins pod cannot be ready
$oc get pod -w -o wide
NAME               READY     STATUS    RESTARTS   AGE       IP            NODE
jenkins-1-4267z    0/1       Running   0          6s        10.128.0.37   qe-dma2-node-registry-router-2
jenkins-1-deploy   1/1       Running   0          11s       10.128.0.36   qe-dma2-node-registry-router-2

Expected results:
Jenkins pod is ready

Additional info:

Comment 1 Ben Parees 2016-11-22 13:56:55 UTC
it appears the new 0.1.0 sync plugin is blocking jenkins startup, as also seen here:
https://github.com/openshift/jenkins/pull/204

@tdawson can we revert the jenkins image to the 0.0.17 plugin for now, unless Jimmi has a very quick fix on this?

Comment 2 Troy Dawson 2016-11-22 15:44:29 UTC
rpm downgraded:
  jenkins-plugin-openshift-sync-0.0.17-1.el7
Puddles have been updated and synced to mirrors.
Images have been created and pushed to registry.ops
  openshift3/jenkins-1-rhel7:1.651.2-38
  openshift3/jenkins-2-rhel7:2.19-5

Comment 3 Dongbo Yan 2016-11-23 02:41:05 UTC
Test with 
brew-pulp.../openshift3/jenkins-1-rhel7   latest              9edb7f9e5157   
brew-pulp.../openshift3/jenkins-2-rhel7   latest              b5b09fbedfc0 
openshift-login	0.9
openshift-pipeline	1.0.36
openshift-sync	0.0.17

openshift v3.4.0.28+dfe3a66
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

jenkins pod can be ready