Bug 1045027

Summary:	jenkins build failed when upgrade env following 1.1->1.2->2.0
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Cluster Version Operator	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED WONTFIX	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0.0	CC:	bleanhar, erich, jialiu, libra-onpremise-devel, lmeyer
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-19 13:49:04 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:

Description Johnny Liu 2013-12-19 13:30:10 UTC

Description of problem:
When upgrade app with jenkins-client following 1.1->1.2->2.0 path, jenkins build always failed.

Version-Release number of selected component (if applicable):
openshift-enterprise-release-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-upgrade-node-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-upgrade-broker-2.0.0c-1.git.21.e364d06.el6op.noarch
openshift-enterprise-yum-validator-2.0.0c-1.git.21.e364d06.el6op.noarch


How reproducible:
Always

Steps to Reproduce:
1.set ose-1.1 env
2.create a scalable app and add jenkins-client on it.
3.upgrade env to 1.2
4.remove jenkins client from app and add a new one, this is addressed to user when upgrade ose-1.1 to ose-1.2
5.do git push, jenkins build succeed.
6.upgrade env to 2.0
7.do git push to trigger jenkins build.

Actual results:
Fail to jenkins build, seen from jenkins server log, get the following error:
<--snip-->
INFO: Requesting GET with protocol 1.2 on https://broker.rhn.com/broker/rest/api
Dec 19, 2013 7:42:00 AM hudson.plugins.openshift.OpenShiftCloud provision
WARNING: Caught java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.rhn.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert:  unrecognized_name. Will retry 2 more times before canceling build.
Dec 19, 2013 7:42:05 AM hudson.plugins.openshift.OpenShiftCloud getOpenShiftConnection
INFO: Initiating Java Client Service - Configured for OpenShift Server https://broker.rhn.com
Dec 19, 2013 7:42:05 AM com.openshift.internal.client.RestService request
INFO: Requesting GET with protocol 1.2 on https://broker.rhn.com/broker/rest/api
Dec 19, 2013 7:42:05 AM hudson.plugins.openshift.OpenShiftCloud provision
<--snip-->

Then try to destroy jenkins server app, re-create a new one, and add jenkins client to this app, do git push, this time, even no any jenkins build is triggered, just a common git push. Seen from jenkins app UI, found my jenkins job is in disabled status.

Expected results:
Jenkin build should work fine.

Additional info:
If setup ose-1.2 env, create app and embed jenkins client, upgrade to 2.0, it is working well.

Comment 2 Luke Meyer 2014-01-09 15:11:41 UTC

I don't think Jenkins makes it through the 1.1 => 1.2 upgrade. This is noted discreetly under "Known Upgrade Issues" at https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/1/html-single/1.2_Release_Notes/index.html#chap-OpenShift_Enterprise-1.2_Release_Notes-Upgrading_to_prod_1.2 (just before the "known issues" section).

If you agree this is the reason for the problem, then this is probably a CANTFIX bug.

Comment 3 Brenton Leanhardt 2014-01-09 15:15:41 UTC

I was thinking the reporter was following the suggestions for 1.1 => 1.2 by removing the jenkins-client and then re-adding it.  However, looking at the release notes again shows that you actually have to delete the jenkins app too. :/.

I'd say this is CANTFIX.

Comment 4 Johnny Liu 2014-01-09 15:26:08 UTC

Toady I re-test this issue following http://etherpad.corp.redhat.com/ose-2-0-upgrade-2014-01-07.

After upgrade env from 1.1 => 2.0, even I destroy jenkins app, re-add jenkins-client to app. jenkins build still does not work.

It always show the following error in jenkins app log:
<--snip-->
INFO: Requesting GET with protocol 1.2 on https://broker.rhn.com/broker/rest/api
Dec 19, 2013 7:42:00 AM hudson.plugins.openshift.OpenShiftCloud provision
WARNING: Caught java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.rhn.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert:  unrecognized_name. Will retry 2 more times before canceling build.
Dec 19, 2013 7:42:05 AM hudson.plugins.openshift.OpenShiftCloud getOpenShiftConnection
INFO: Initiating Java Client Service - Configured for OpenShift Server https://broker.rhn.com
Dec 19, 2013 7:42:05 AM com.openshift.internal.client.RestService request
INFO: Requesting GET with protocol 1.2 on https://broker.rhn.com/broker/rest/api
Dec 19, 2013 7:42:05 AM hudson.plugins.openshift.OpenShiftCloud provision
<--snip-->

Comment 5 Brenton Leanhardt 2014-01-09 15:31:06 UTC

Let's reopen this and figure out the root cause to make sure there isn't something else going on (and how we could avoid situations like this in the future).  This one definitely seems odd.