Bug 811761 - Jenkins slave DNS errors causing builds to halt
Summary: Jenkins slave DNS errors causing builds to halt
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: Bill DeCoste
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-11 22:37 UTC by Nam Duong
Modified: 2015-05-15 01:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-17 14:52:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nam Duong 2012-04-11 22:37:54 UTC 
Description of problem:
A user posted to the forums: https://www.redhat.com/openshift/community/forums/openshift/issue-creating-jenkins-app-dns

I'm able to reproduce this user's problem with a sample php application (while trying to rule out DIY):
steps:
rhc app create -a static -t php-5.3
rhc app create -a ci -t jenkins-1.4
rhc app cartridge add -a static -c jenkins-client-1.4
modify file and push to queue a build
rhc app tail -a ci

Attached is the log.  Do we know of any workarounds for the user?
Comment 1 Mike McGrath 2012-04-13 16:20:30 UTC 
Timeout for DNS probably too short.
Comment 2 Bill DeCoste 2012-04-13 16:24:58 UTC 
I recently increased the default DNS timeout from 60000ms to 300000ms. This is configurable in the job config.
Comment 3 Bill DeCoste 2012-04-16 14:20:15 UTC 
This is not a bug. Please have the user increase their timeout in the jenkins job config.
Comment 4 Meng Bo 2012-04-17 05:41:27 UTC 
checked on devenv_1724 with jenkins-plugin-openshift-0.5.13,
the default timeout is 300000, and this issue won't reproduce,
mark this bug as verified.
Note You need to log in before you can comment on or make changes to this bug.