Red Hat Bugzilla – Bug 1425320
Warning from build-controller appears about failed to create pod since it already exists
Last modified: 2017-07-24 10:11 EDT
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:
fix is in https://github.com/openshift/origin/pull/13048
backport to 1.5: https://github.com/openshift/origin/pull/13075
This has been merged into ocp and is in OCP v3.5.0.34 or newer.
Verified on below version: openshift v3.5.0.35 kubernetes v1.5.2+43a9be4 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/RHBA-2017:0884
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