Description of problem: on stage: jenkins build an app, and the output show it is Waiting for build to schedule Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.create an app(eg jbossas,php) with jenkins-client-1.4 embedded 2.make some change in the app's repo 3.git commit && git push 4.it always shows waiting for build to schedule, no matter how long waited Actual results: Counting objects: 7, done. Delta compression using up to 4 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 360 bytes, done. Total 4 (delta 2), reused 0 (delta 0) remote: Executing Jenkins build. remote: remote: You can track your build at https://jkss-jhou.stg.rhcloud.com/job/p1-build remote: remote: Waiting for build to schedule................................................................................................................................................................................................................................................................................................................................................................................ please find jenkins.log in the attachments. Expected results: should git push successfully Additional info:
stage version 2.0.13
Created attachment 594989 [details] jenkins log please find logs in the attachments
Created attachment 595109 [details] More research from stage I'm adding some more research from stage detailing the various exceptions presented at each step of the test scenario. Looks like the Jenkins plugin is having trouble communicating with the broker via the legacy API to provision a builder node.
This is working fine on a devenv but stage for some reason is getting socket timeouts when Jenkins is trying to hit the broker: Caused by: java.net.SocketTimeoutException: connect timed out when trying to hit https://stg.openshift.redhat.com/broker/userinfo
Can we get the broker log?
We've watched the broker logs in stage while Jenkins attempts to provision the node on a 1 minute interval. For each failed request from Jenkins, there is a corresponding log in the broker: ActionController::RoutingError (No route matches "/") This is the only related server side log which has been found so far.
There was a connectivity issue isolated to stage preventing jenkins from communicating with the broker. The issue was caused by a stale /etc/hosts entry for the stage host, causing the jenkins http client to be unable to resolve stage. Stage has been corrected, and Jenkins now functions properly.
verified on statge 2.0.13 1.create jenkins app 2.create app with jenkins-client enabled 3.make some change in app's repo an git push jenkins build works well now.