Bug 1705128 - Builds Do Not Expose Evictions on Build Pods as Specific Errors
Summary: Builds Do Not Expose Evictions on Build Pods as Specific Errors
Keywords:
Status: CLOSED DUPLICATE of bug 1689061
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.11.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Adam Kaplan
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-01 14:54 UTC by Steve Kuznetsov
Modified: 2019-05-14 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: if a build pod was evicted, build reported a GenericBuildFailure Consequence: cluster administrators could not determine why builds failed if the node was under resource pressure Fix: new failure reason `BuildPodEvicted` added Result: builds that fail due to pod eviction report `BuildPodEvicted` in their status reason
Clone Of:
Environment:
Last Closed: 2019-05-14 15:51:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1689061 0 unspecified CLOSED Evicted builds don't have a specific status reason, instead are GenericBuildFailure 2021-02-22 00:41:40 UTC

Description Steve Kuznetsov 2019-05-01 14:54:03 UTC
When a build has its pod evicted, the "GenericBuildFailed: Generic Build failure" is used, which is opaque.

Comment 1 Adam Kaplan 2019-05-14 14:43:52 UTC
Note - this was fixed in 4.1.0 via #1689061 [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1689061

Comment 2 Steve Kuznetsov 2019-05-14 15:51:35 UTC

*** This bug has been marked as a duplicate of bug 1689061 ***


Note You need to log in before you can comment on or make changes to this bug.