Bug 836184
Summary: | Jenkins build always shows "waiting for build to schedule" in stage | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OKD | Reporter: | Jianwei Hou <jhou> | ||||||
Component: | Containers | Assignee: | Dan Mace <dmace> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 2.x | CC: | adietish, mpatel, rmillner, wdecoste | ||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2012-07-13 23:43:44 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: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Jianwei Hou
2012-06-28 09:52:56 UTC
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. |