Bug 1593139 - Unqualified image in non docker hub registry with specific tag can not be pulled
Summary: Unqualified image in non docker hub registry with specific tag can not be pulled
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Seth Jennings
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks: 1593142
TreeView+ depends on / blocked
 
Reported: 2018-06-20 07:44 UTC by weiwei jiang
Modified: 2018-07-26 20:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1593142 (view as bug list)
Environment:
Last Closed: 2018-07-26 20:36:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description weiwei jiang 2018-06-20 07:44:36 UTC 
Description of problem:
When try to create a pod with unqualified image which in non docker hub registry with specific tag, pod will go in ImagePullBackOff status.

Follow with https://bugzilla.redhat.com/show_bug.cgi?id=1583500#c46

Version-Release number of selected component (if applicable):
# oc version 
oc v3.10.1
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://qe-wjiang-310f2-master-etcd-1:8443
openshift v3.10.1
kubernetes v1.10.0+b81c8f8


How reproducible:
Always

Steps to Reproduce:
1. Create pod with image from non docker dub with specific tag
oc run test --image=openshift3/metrics-heapster:v3.10.1 --command sleep 10d
2. Check pod status
3.

Actual results:
# oc get pods 
NAME                       READY     STATUS             RESTARTS   AGE
test-1-deploy              1/1       Running            0          46s
test-1-x5sf9               0/1       ImagePullBackOff   0          44s



Expected results:
Pod should be running with expected image

Additional info:
Note You need to log in before you can comment on or make changes to this bug.