Bug 786371 - Jbossas app's jenkins build hang there.
Summary: Jbossas app's jenkins build hang there.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 1.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 08:56 UTC by Johnny Liu
Modified: 2012-02-02 23:55 UTC (History)
3 users (show)

Fixed In Version: rhc-node-0.85.20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 23:55:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Johnny Liu 2012-02-01 08:56:23 UTC
Description of problem:
Jbossas app's jenkins build hang there.

Version-Release number of selected component (if applicable):
rubygem-cloud-sdk-node-0.3.16-1.el6_2.noarch
rubygem-cloud-sdk-common-0.3.14-1.el6_2.noarch
rubygem-cloud-sdk-controller-0.3.21-1.el6_2.noarch
rhc-broker-0.85.27-1.el6_2.noarch


How reproducible:
Always

Steps to Reproduce:
1. Create jbossas app, and embed jenkins client to it.
2. Do git push to trigger jenkins build.
3.
  
Actual results:
$ git commit -a -m "xx";git push 
[master 3f98dbd] xx
 1 files changed, 1 insertions(+), 1 deletions(-)
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 274 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Executing Jenkins build.
remote: 
remote: You can track your build at http://jenkins-j1.dev.rhcloud.com/job/jbosstest-build
remote: 
remote: Waiting for build to schedule.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................^CKilled by signal 2.



Jenkins log:
<--snip-->
INFO: Started provisioning jbosstest-build from OpenShift Cloud with 1 executors. Remaining excess workload:-0.6968255
com.openshift.express.client.OpenShiftEndpointException: Could not configure application "jbosstestbldr" at "https://10.76.213.7/broker/cartridge"
	at com.openshift.express.client.OpenShiftService.sendRequest(OpenShiftService.java:366)
	at com.openshift.express.client.OpenShiftService.requestApplicationAction(OpenShiftService.java:289)
	at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:178)
	at hudson.plugins.openshift.OpenShiftSlave.createApp(OpenShiftSlave.java:215)
	at hudson.plugins.openshift.OpenShiftSlave.provision(OpenShiftSlave.java:185)
	at hudson.plugins.openshift.OpenShiftCloud$2.call(OpenShiftCloud.java:463)
	at hudson.plugins.openshift.OpenShiftCloud$2.call(OpenShiftCloud.java:457)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: com.openshift.express.internal.client.httpclient.InternalServerErrorException: {"broker":"1.1.1","exit_code":1,"messages":"","debug":"","api":"1.1.2","data":"","api_c":["placeholder"],"broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"result":"No nodes available.  If the problem persists please contact Red Hat support."}
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:110)
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:73)
	at com.openshift.express.client.OpenShiftService.sendRequest(OpenShiftService.java:357)
	... 11 more
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://10.76.213.7/broker/cartridge
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
	at com.openshift.express.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:68)
	... 12 more
Feb 1, 2012 3:42:45 AM hudson.plugins.openshift.OpenShiftSlave stopApp
INFO: Slave stopping application...
<--snip-->


Log into instance to make sure a "large" instance is running.
# mc-ping
ip-10-80-173-6                           time=123.17 ms
ip-10-76-213-7                           time=127.32 ms
ip-10-10-215-236                         time=130.65 ms


---- ping statistics ----
3 replies max: 130.65 min: 123.17 avg: 127.05
[root@ip-10-76-213-7 bin]# mc-facts -I ip-10-10-215-236 node_profile
Report for fact: node_profile

        large                                   found 1 times



Expected results:
Jenkins build succeed.

Additional info:
Jbossas app's jenkins build works fine on devenv_stage_11.
After that I upgrade rhc package to the latest ones, and this issue is seen.
So I mark this bug as "Regression"

Comment 1 Johnny Liu 2012-02-01 09:16:53 UTC
Rack app's jenkins build is working fine.

Comment 2 Johnny Liu 2012-02-01 09:24:39 UTC
(In reply to comment #1)
> Rack app's jenkins build is working fine.

A strange issue, after jbossas app's jenkins build hang there, then trigger rack app's jenkins build, rack app's jenkins build will also hung there, after remove jbossas jenkins build job in jenkins UI, rack app's jenkisn build succeed.

Comment 3 jizhao 2012-02-02 07:08:57 UTC
Verified on QE_devenv-stage_119.

Comment 4 Mrunal Patel 2012-02-02 23:55:48 UTC
Closing verified bugs.


Note You need to log in before you can comment on or make changes to this bug.