Bug 1293829
Summary: | Return 'read time out‘ in jenkins webconsole when trigger a build more than 2 minites | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.0 | CC: | aos-bugs, bleanhar, bparees, gmontero, jokerman, mmccomas, pruan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-26 19:20:33 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: |
Description
XiuJuan Wang
2015-12-23 08:15:50 UTC
Gabe, is this related to the plugin verison regression to 1.0.3? or a new bug? This is not related to the 1.0.3 / 1.0.4 issue. However, the ability to change the timeout value that the tester asked for already exists. Now, is it properly documented .... it would be fair to say it is not. If everyone agrees, we can use this defect to get the repo's readme updated to properly explain how to change the timeout value. I've updated the README at https://github.com/openshift/jenkins-plugin with some instructions on how to override the timeouts. Sending to QA to peruse the README and give it a try. I think we should also default higher than 2 minutes. Maybe 5. Changed 'Wait interval'(default is 60000) of 'OpenShift Build Verification' to 120000 'Wait interval'(default is 120000) of 'OpenShift Builder' to 600000 'Wait interval'(default is 60000) of 'OpenShift Deployer' to 120000 Then trigger new build in jenkins webconsole, could correct build status with long time build. Mark this bug as verified Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2016:0070 |