Bug 1332546

Summary: Containers not running because openshift3/ose-pod:v3.2.0.20 is failing to pull
Product: OpenShift Online Reporter: Cesar Wong <cewong>
Component: Image RegistryAssignee: Dan Mace <dmace>
Status: CLOSED CURRENTRELEASE QA Contact: Wei Sun <wsun>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.xCC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-23 15:08:51 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:

Description Cesar Wong 2016-05-03 12:58:22 UTC
Description of problem:

When trying to run a new build, the build pod never starts. 'oc get events' returns:

FIRSTSEEN   LASTSEEN   COUNT     NAME                  KIND      SUBOBJECT   TYPE      REASON       SOURCE                                   MESSAGE
13m         3m         7         simple-ruby-1-build   Pod                   Warning   FailedSync   {kubelet ip-172-31-14-20.ec2.internal}   Error syncing pod, skipping: failed to "StartContainer" for "POD" with ErrImagePull: "Error: image openshift3/ose-pod:v3.2.0.20 not found"

Version-Release number of selected component (if applicable):
Online, current version (3.2)

How reproducible:
Always

Steps to Reproduce:
1. oc new-app https://github.com/csrwng/simple-ruby.git
2. Wait for build to start

Actual results:

Build never starts

Expected results:

Build starts and simple app is deployed.

Additional info:

Comment 1 Dan Mace 2016-05-03 13:25:55 UTC
I suspect the problem is that the version being pulled is v3.2.0.20 and not v3.2.0.40. The old tag could have been pruned from the registry. I'll follow up with Ops to solve this.

Comment 2 Dan Mace 2016-05-03 13:29:37 UTC
Actually, that image exists, but you can't pull it without a fully qualified pullspec with a registry, e.g. registry.qe.openshift.com/openshift3/ose-pod:v3.2.0.20.

Comment 3 Dan Mace 2016-05-03 14:20:08 UTC
Ops missed a step during cluster setup, causing the images to be unavailable. They ran the step, and builds seem to work now.

Comment 4 Wei Sun 2016-05-04 01:55:02 UTC
Verify this bug,now the build and deployment work.