Bug 1436391
Summary: | Some build failures missing detailed status | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Vikas Laad <vlaad> |
Component: | Build | Assignee: | Corey Daley <cdaley> |
Status: | CLOSED ERRATA | QA Contact: | Vikas Laad <vlaad> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.1 | CC: | aos-bugs, bparees, jminter, mifiedle, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Code was not setting status reason and status message for certain failures
Consequence: Missing status reason and status message for certain failures
Fix: Added code that sets status reason and status message
Result: Status reason and message are now set
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-10 05:20:02 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: | |||
Bug Depends On: | 1442875 | ||
Bug Blocks: |
Description
Vikas Laad
2017-03-27 20:18:43 UTC
Not a blocker since we never expected to provide failure reasons for all possible failures, but we'll fix this to return a generic failure reason and direct the user to the logs. Submitted pull request https://github.com/openshift/origin/pull/13590 This has been merged into ocp and is in OCP v3.6.28 or newer. Verification of this bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1442875 apologies for the noise, updated wrong bug :( Verified in the following version, I see following line for the same kind of build failure proj3 cakephp-mysql-example-129 Source Git@0014dde Failed (ContainerCommitFailed) 4 minutes ago 10s root@ip-172-31-4-211: ~ # openshift version openshift v3.6.74 kubernetes v1.6.1+5115d708d7 etcd 3.1.0 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/RHEA-2017:1716 |