Bug 1332546 - Containers not running because openshift3/ose-pod:v3.2.0.20 is failing to pull
Summary: Containers not running because openshift3/ose-pod:v3.2.0.20 is failing to pull
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image Registry
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dan Mace
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 12:58 UTC by Cesar Wong
Modified: 2016-05-23 15:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-23 15:08:51 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.