Bug 1425320

Summary: Warning from build-controller appears about failed to create pod since it already exists
Product: OpenShift Container Platform Reporter: Wenjing Zheng <wzheng>
Component: BuildAssignee: Ben Parees <bparees>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: aos-bugs, bparees, cewong, knakayam, pweil, 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:
: 1426776 (view as bug list) Environment:
Last Closed: 2017-03-09 04:08:15 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:    
Bug Blocks: 1426776    

Description Wenjing Zheng 2017-02-21 08:17:10 UTC
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:

Comment 1 Ben Parees 2017-02-22 15:11:49 UTC
fix is in https://github.com/openshift/origin/pull/13048

Comment 2 Ben Parees 2017-02-23 11:50:08 UTC
backport to 1.5: https://github.com/openshift/origin/pull/13075

Comment 3 Troy Dawson 2017-02-24 20:02:00 UTC
This has been merged into ocp and is in OCP v3.5.0.34 or newer.

Comment 5 Wenjing Zheng 2017-02-28 10:05:24 UTC
Verified on below version:
openshift v3.5.0.35
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Comment 6 errata-xmlrpc 2017-04-12 19:13:27 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-2017:0884

Comment 7 Kenjiro Nakayama 2017-07-18 05:15:32 UTC
Hi Ben,

One customer hit the same issue on 3.4.1.12. Could you please backport the fix to 3.4? (If necessary, I will file new ticket for 3.4.)
I am attaching the logs to this ticket in private.

[1]
[root@drlosm01 ~]# openshift version
openshift v3.4.1.12
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0