Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1436391 - Some build failures missing detailed status
Some build failures missing detailed status
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build (Show other bugs)
3.5.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Corey Daley
Vikas Laad
:
Depends On: 1442875
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-27 16:18 EDT by Vikas Laad
Modified: 2017-08-16 15 EDT (History)
5 users (show)

See Also:
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 01:20:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Description Vikas Laad 2017-03-27 16:18:43 EDT
Description of problem:
Some of the build failures are missing the reason when docker is running out of space.

proj9       cakephp-mysql-example-27   Source    Git@0014dde   Failed                               About a minute ago   

root@ip-172-31-25-76: ~/svt/openshift_performance/ci/scripts # oc logs -n proj40      cakephp-mysql-example-38-build
no such container: "2a0a03f3a808dc0d11391b4bf83d650146abb264f3be617f7dd69134aa5e1229"root@ip-172-31-25-76: ~/svt/openshift_performance/ci/scripts # oc logs -n proj9       cakephp-mysql-example-27-build
Cloning "https://github.com/redhat-performance/cakephp-ex.git" ...
        Commit: 0014ddebb91bc7dff3a1dabfbd7b51da762a6677 (made changes to enable database example)
        Author: ofthecure <robdean.smith@gmail.com>
        Date:   Mon Apr 25 14:33:06 2016 -0400
DEPRECATED: Use .s2i/bin instead of .sti/bin
error: build error: Error response from daemon: {"message":"devmapper: Thin Pool has 5328 free data blocks which is less than minimum required 6083 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior"}


Version-Release number of selected component (if applicable):
openshift v3.5.3
kubernetes v1.5.2+43a9be4
etcd 3.1.0

How reproducible:


Steps to Reproduce:
1. Run concurrent builds and make sure docker runs out of space on worker nodes
2. See the failed builds

Actual results:
Reason for build failure is missing

Expected results:
Should show reason something like FailureToAssembleContainer

Additional info:
will upload master logs.
Comment 2 Ben Parees 2017-03-30 09:23:30 EDT
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.
Comment 3 Corey Daley 2017-03-30 12:28:00 EDT
Submitted pull request https://github.com/openshift/origin/pull/13590
Comment 4 Troy Dawson 2017-04-12 08:59:42 EDT
This has been merged into ocp and is in OCP v3.6.28 or newer.
Comment 6 Vikas Laad 2017-04-28 10:00:16 EDT
Verification of this bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1442875
Comment 7 Jim Minter 2017-05-08 06:18:28 EDT
apologies for the noise, updated wrong bug :(
Comment 8 Vikas Laad 2017-05-11 14:14:34 EDT
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
Comment 10 errata-xmlrpc 2017-08-10 01:20:02 EDT
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

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