Bug 773606

Summary:	Config file and openshift plugin is not updated for existing jenkins app after upgrade packages and run migrate script.
Product:	OKD	Reporter:	Johnny Liu <jialiu>
Component:	Containers	Assignee:	Dan McPherson <dmcphers>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.x
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhc-node-0.84.24-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-16 21:10:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Johnny Liu 2012-01-12 12:07:30 UTC

Description of problem:
1. According to https://bugzilla.redhat.com/show_bug.cgi?id=771862#c1, now config.xml has been updated, but after update packages and run migrate script in old instance (devenv_stage_110), checked config.xml in my jenkins app, found it was still using old url. (e.g: <url>https://localhost</url>)
NOTE:
Curiously, even using old conf file, the first jenkins build can be finished successfully.

2. After the first successful jenkins build, trigger the second jenkins build, this time jenkins build hang there.
<--snip-->
remote: Waiting for build to schedule...................................
<--snip-->

Check jenkins log:
<--snip-->
Jan 12, 2012 7:02:27 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: User has consumed 4 applications.
Jan 12, 2012 7:02:27 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: Capacity remaining - checking for existing type...
Jan 12, 2012 7:02:27 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: Found an existing builder. Not provisioning...
Jan 12, 2012 7:02:27 AM hudson.plugins.openshift.OpenShiftCloud provision
INFO: Not provisioning new builder...
Jan 12, 2012 7:02:27 AM hudson.plugins.openshift.OpenShiftCloud provision
INFO: Provisioning new node for workload = 1 and label = racktest-build
Jan 12, 2012 7:02:29 AM hudson.plugins.openshift.OpenShiftCloud getSlaves
INFO: Found existing slave for: racktestbldr
Jan 12, 2012 7:02:29 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: Checking capacity
Jan 12, 2012 7:02:30 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: User has consumed 4 applications.
Jan 12, 2012 7:02:30 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: Capacity remaining - checking for existing type...
Jan 12, 2012 7:02:30 AM hudson.plugins.openshift.OpenShiftCloud shouldProvision
INFO: Found an existing builder. Not provisioning...
Jan 12, 2012 7:02:30 AM hudson.plugins.openshift.OpenShiftCloud provision
INFO: Not provisioning new builder...
<--snip-->

This info is very similar with info in bug 752707.
I guess this is caused by jenkins is using old openshift plugin with some bug.

I guess migrate script need be updated to fix this issue.

Version-Release number of selected component (if applicable):
migrate-2.0.3
jenkins-plugin-openshift-0.4.16-1.el6_2.x86_64
jenkins-1.409.3-1.2.noarch
rhc-cartridge-jenkins-1.4-0.84.6-1.el6_2.noarch
rhc-cartridge-jenkins-client-1.4-0.18.4-1.el6_2.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a app with jenkins enabled against old instance (stage_110)
2. Upgrade all the packages to the latest.
# yum update -y
3. Running migrate script for li git repo.
# ./migrate-2.0.3
4. Do some change, and jenkins build works fine.
5. Do some change again to tigger jenkins build.

Actual results:
Jenkins build hang there.
$ git commit
<--snip-->
remote: Waiting for build to schedule......................................................................
<--snip-->

Expected results:
After upgrade, jenkins build should work fine, and jenkins plugin should be updated to the latest version.

Additional info:

Comment 1 Dan McPherson 2012-01-12 14:59:42 UTC

For step 3, are you running the entire migrate script or are you limiting it to a subset of rhlogins?  And does the migrate finish successfully?

Comment 2 Dan McPherson 2012-01-12 15:28:12 UTC

You can ignore my last comment.  I looked onto the machine and found an issue with the migration.

Comment 3 Dan McPherson 2012-01-12 15:42:30 UTC

The other thing to note is you should so a service libra restart to pick up the new jenkins plugin after a migrate.  They do this in ops currently.

Comment 4 Johnny Liu 2012-01-13 05:21:19 UTC

Verified with new migrate script, and PASSED.

After upgrade express server, run migrate, config.xml is updated, restart libra service, do git commit, jenkins build works fine.