Bug 1533181

Summary:	[3.6] Failed docker builds leave temporary containers on node
Product:	OpenShift Container Platform	Reporter:	Carsten Lichy-Bittendorf <clichybi>
Component:	Build	Assignee:	Ben Parees <bparees>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	aos-bugs, bparees, dcaldwel, dyan, smunilla
Target Milestone:	---
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The OpenShift Docker builder invokes the Docker build API without the ForceRmTemp flag Consequence: Containers from failed builds remain on the node where the build ran. These containers are not recognized by the kubelet for gc and are therefore accumulated until the node runs out of space. Fix: Modified the Docker build API call from the OpenShift Docker builder to force the removal of temporary containers. Result: Failed containers no longer remain on the node where a Docker build ran.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-12 06:01:18 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:	1512679
Bug Blocks:

Description Carsten Lichy-Bittendorf 2018-01-10 16:40:25 UTC

Description of problem:

https://bugzilla.redhat.com/1512679 was resolved for OCP 3.7 while the customer is on OCP 3.6. Please consider a back-porting.

Comment 1 Ben Parees 2018-01-10 16:54:56 UTC

https://github.com/openshift/ose/pull/994

Comment 3 Dongbo Yan 2018-01-17 02:47:33 UTC

this bug should be a back-porting to 3.6.z, not 3.9, please remove from wrong errata.
Since there is no new puddle built, move to modified

Comment 5 Dongbo Yan 2018-02-01 07:25:10 UTC

Verified
openshift v3.6.173.0.101
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

no temporary containers exist, could move to verified status

Comment 7 Ben Parees 2018-03-06 14:54:53 UTC

Carsten, that is a question for Sam.

But i will go ahead and move it to ON_QA at least.

Comment 14 errata-xmlrpc 2018-04-12 06:01:18 UTC

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/RHBA-2018:1106