Bug 1271985

Summary: [devexp_public_692]Build fails if build time exceeds defined completionDeadlineSeconds even build is in running state
Product: OKD Reporter: Wenjing Zheng <wzheng>
Component: BuildAssignee: Maciej Szulik <maszulik>
Status: CLOSED CURRENTRELEASE QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, bparees
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: 2015-11-23 21:13:15 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 Wenjing Zheng 2015-10-15 08:40:30 UTC
Description of problem:
When completionDeadlineSeconds to a small number in buildconfig,build get failed even it is in running state.

Version-Release number of selected component (if applicable):
openshift v1.0.6-610-g1bc373b
kubernetes v1.1.0-alpha.1-653-g86b4e77

How reproducible:
always

Steps to Reproduce:
1. Add below setting to buildconfig part
"spec":{
        "completionDeadlineSeconds": 30,
        
2. Create build with it
3. Check build status

Actual results:
Build get failed even it is in normal running state.

Expected results:
This value should be only work when build keeps pending.

Additional info:

Comment 1 Ben Parees 2015-10-19 01:25:47 UTC
The completiondeadline is a maximum duration for the build to reach a "complete" state, so it is expected that it would go from "running" to "failed" if the time is exceeded.

Is there something in the documentation that lead you to think the build should not be failed?  I'm going to set this back to ON_QA but if the documentation is wrong, please reopen and we'll get the docs fixed.

Comment 2 Wenjing Zheng 2015-10-19 03:03:52 UTC
Thanks for your confirm, Ben! Since the card says for pending build, so report this bug, just checked documentation carefully, it has no issue. Will verify this bug.
$openshift version
openshift v1.0.6-691-g3d79bc3
kubernetes v1.1.0-alpha.1-653-g86b4e77
etcd 2.1.2