Bug 804276 - Jenkins builds fail the first few times after migration
Summary: Jenkins builds fail the first few times after migration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-17 08:38 UTC by Rob Millner
Modified: 2015-05-14 22:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:30:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 804010 0 high CLOSED jenkins push build will hang there after migration 2021-02-22 00:41:40 UTC

Internal Links: 804010

Description Rob Millner 2012-03-17 08:38:59 UTC 
After migration from 2.0.6 to 2.0.7, Jenkins application builds fail.

Logging into the Jenkins console and retrying the build a few times or waiting a long time seems to resolve the issue (a new builder gear).

Since the problem goes away on its own, calling this a medium.
Comment 1 Rob Millner 2012-03-17 08:43:59 UTC 
This should have been addressed by commit 2aa3651, but there's something which is temporarily holding on to the old value.

The slave.jar process may be the culprit.
java -jar /var/lib/libra/65579fd16efd43fe84a8dd085398c809/rlm7stg4bldr/data//jenkins/slave.jar

Its environment remains static from the time of launch.
Comment 2 Rob Millner 2012-03-23 02:35:31 UTC 
We're passed the post-migration window for this issue to show up and doesn't have appeared to affect anybody.
Comment 3 Meng Bo 2012-03-30 02:56:28 UTC 
Verified with latest migration scripts on devenv_1679.
Issue has been fixed.
Note You need to log in before you can comment on or make changes to this bug.