Bug 1426776

Summary:	Warning from build-controller appears about failed to create pod since it already exists
Product:	OpenShift Container Platform	Reporter:	Troy Dawson <tdawson>
Component:	Build	Assignee:	Cesar Wong <cewong>
Status:	CLOSED NOTABUG	QA Contact:	Wenjing Zheng <wzheng>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.1	CC:	aos-bugs, bparees, tdawson, wzheng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1425320	Environment:
Last Closed:	2017-02-24 20:06: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:	1425320
Bug Blocks:

Description Troy Dawson 2017-02-24 20:04:03 UTC

+++ This bug was initially created as a clone of Bug #1425320 +++

Description of problem:
Build change to New state for a while since warning about builder pod already exists when describe it:
Events:
  FirstSeen    LastSeen    Count    From                    SubObjectPath            Type        Reason        Message
  ---------    --------    -----    ----                    -------------            --------    ------        -------
  4m        4m        1    {default-scheduler }                            Normal        Scheduled    Successfully assigned ruby-ex-1-build to ip-172-18-11-153.ec2.internal
  4m        4m        1    {kubelet ip-172-18-11-153.ec2.internal}    spec.containers{sti-build}    Normal        Pulled        Container image "registry.ops.openshift.com/openshift3/ose-sti-builder:v3.5.0.32-1" already present on machine
  4m        4m        1    {kubelet ip-172-18-11-153.ec2.internal}    spec.containers{sti-build}    Normal        Created        Created container with docker id 25cb4a3a48f1; Security:[seccomp=unconfined]
  4m        4m        1    {kubelet ip-172-18-11-153.ec2.internal}    spec.containers{sti-build}    Normal        Started        Started container with docker id 25cb4a3a48f1
  3m        3m        2    {build-controller }                            Warning        FailedCreate    Pod already exists: wzheng1/ruby-ex-1-build

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

How reproducible:
always

Steps to Reproduce:
1. Create a project
2. oc new-app ruby:2.2~https://github.com/openshift/ruby-ex.git 
3. Check build status and description

Actual results:
1. Build keeps in New for a while
$ oc get builds --watch
NAME        TYPE      FROM          STATUS    STARTED         DURATION
ruby-ex-1   Source    Git@855ab2d   New       2 minutes ago   
NAME        TYPE      FROM          STATUS    STARTED         DURATION
ruby-ex-1   Source    Git@855ab2d   New       2 minutes ago   
ruby-ex-1   Source    Git@855ab2d   Complete   2 minutes ago   46s
2. Warning about builder pod already exists in build description

Expected results:
Should be no such warning 

Additional info:

--- Additional comment from Ben Parees on 2017-02-22 10:11:49 EST ---

fix is in https://github.com/openshift/origin/pull/13048

--- Additional comment from Ben Parees on 2017-02-23 06:50:08 EST ---

backport to 1.5: https://github.com/openshift/origin/pull/13075

--- Additional comment from Troy Dawson on 2017-02-24 15:02:00 EST ---

This has been merged into ocp and is in OCP v3.5.0.34 or newer.

Comment 1 Troy Dawson 2017-02-24 20:06:18 UTC

Sorry, cloned the wrong bug.