Bug 1384332 - Deploying registry-console pod with ansible (deployment_subtype=registry) doesn't set image prefix
Summary: Deploying registry-console pod with ansible (deployment_subtype=registry) doe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.3.1
Assignee: Andrew Butcher
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-13 06:46 UTC by Kenjiro Nakayama
Modified: 2016-11-11 13:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
There was an error in how
Clone Of:
Environment:
Last Closed: 2016-11-11 13:56:05 UTC
Target Upstream Version:

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

Description Kenjiro Nakayama 2016-10-13 06:46:45 UTC 
Description of problem:

  Deploying registry-console with ansible (deployment_subtype=registry) doesn't set image prefix

Version-Release number of selected component (if applicable):

  atomic-openshift-utils-3.3.28-1.git.0.762256b.el7.noarch

How reproducible:

Steps to Reproduce:
1. Install master and registry with all-in-one as desribed in https://docs.openshift.com/container-platform/3.3/install_config/install/stand_alone_registry.html#registry-advanced-installation

Actual results:

   It sets the image as below:

     # oc get dc registry-console -o yaml |grep image
          image: registry-console:3.3


Expected results:

  It should set image as:

    # oc get dc registry-console -o yaml |grep image
            image: openshift3/registry-console:3.3

Additional info:

  Because of this issue, pod beomes ImagePullBackOff after the installation

   # oc get pod
   NAME                       READY     STATUS             RESTARTS   AGE
   docker-registry-2-8i0tk    1/1       Running            0          11m
   registry-console-1-ix1n1   0/1       ImagePullBackOff   0          3m
   router-1-rk5qu             1/1       Running            0          11m


   # oc get event 

   LASTSEEN                    FIRSTSEEN                   COUNT     NAME                       KIND      SUBOBJECT   TYPE      REASON       SOURCE                   MESSAGE
   2016-10-13T15:35:30+09:00   2016-10-13T15:31:32+09:00   14        registry-console-1-ix1n1   Pod                   Warning   FailedSync   {kubelet 10.64.221.28}   Error syncing pod, skipping: failed to "StartContainer" for "registry-console" with ImagePullBackOff: "Back-off pulling image \"registry-console:3.3\""
    
   2016-10-13T15:35:30+09:00   2016-10-13T15:31:32+09:00   14        registry-console-1-ix1n1   Pod       spec.containers{registry-console}   Normal    BackOff   {kubelet 10.64.221.28}   Back-off pulling image "registry-console:3.3"
Comment 2 Johnny Liu 2016-10-20 16:27:18 UTC 
Verified this bug with openshift-ansible-3.3.38-1.git.0.2637ed5.el7.noarch, and PASS.
Did not set openshift_cockpit_deployer_prefix in inventory host file, run installation, after done, registry-console is deployed successfully.

[root@openshift-141 ~]# oc get po
NAME                       READY     STATUS    RESTARTS   AGE
docker-registry-3-r83pr    1/1       Running   0          3m
registry-console-1-vl7d2   1/1       Running   0          3m


[root@openshift-141 ~]# oc get dc registry-console -o yaml |grep image
        image: registry.access.redhat.com/openshift3/registry-console:3.3
        imagePullPolicy: IfNotPresent
[root@openshift-141 ~]# oc get dc registry-console -o yaml |grep image
        image: registry.access.redhat.com/openshift3/registry-console:3.3
        imagePullPolicy: IfNotPresent
Comment 3 Scott Dodson 2016-11-11 13:56:05 UTC 
Fixed in openshift-ansible-3.3.41-1.git.0.a1a327b.el7 which shipped on October 27th.
Note You need to log in before you can comment on or make changes to this bug.