Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1465828

Summary: [3.5] incorrect registry path in the cfme template packaged
Product: OpenShift Container Platform Reporter: Felix Dewaleyne <fdewaley>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: aos-bugs, fdewaley, gpei, jokerman, mmccomas, sdodson, trankin
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
The CFME templates have been updated to support CFME 4.5.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-16 07:59:16 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 Felix Dewaleyne 2017-06-28 10:00:49 UTC
Description of problem:
incorrect registry path in the cfme template packaged in 3.5.5

Version-Release number of selected component (if applicable):
3.5.5
atomic-openshift-utils-3.5.78-1.git.0.f7be576

How reproducible:
all the time

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:
already fixed in github : https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/v1.5/cfme-templates/cfme-template.yaml

values for dockerImageRepository inccorectly point to "cloudforms" instead of "cloudforms45"

Comment 1 Ben Parees 2017-06-28 13:27:32 UTC
Sending to installer to do whatever backporting/updating needs to be done to pick up the change.

Comment 2 Felix Dewaleyne 2017-07-11 10:00:39 UTC
over bz#1465942 it was pointed out that this isn't the only change required in the template :

"It sounds like the issue was hit because the only change made to the template was to update the repository from cloudforms to cloudforms45 when really all the changes in this patch [1] needed to be made as well. These changes include adding the region PV which would explain the issue you are seeing.

I'll leave a needinfo here for you until you can test this with the complete new template.

[1] https://github.com/openshift/openshift-ansible/pull/4334/files"

Comment 3 Scott Dodson 2017-07-11 12:59:40 UTC
Yeah, I agree. I think that bug should be closed as a dupe of this?

https://github.com/openshift/openshift-ansible/pull/4731 pulls over the complete changes from #4334

Comment 5 Gaoyun Pei 2017-08-09 03:30:34 UTC
Verify this bug with openshift-ansible-3.5.110-1.git.0.6f1f193.el7.noarch.rpm

After a successful ocp-3.5 installation, check the images referred in /usr/share/openshift/examples/cfme-templates/cfme-template.yaml

For POSTGRESQL_IMG_NAME, MEMCACHED_IMG_NAME and APPLICATION_IMG_NAME, they're all pointing to cloudforms45 namespace now.

[root@ip-172-18-3-48 ~]# grep -B 3 registry.access.redhat.com /usr/share/openshift/examples/cfme-templates/cfme-template.yaml 
    name: "POSTGRESQL_IMG_NAME"
    displayName: "PostgreSQL Image Name"
    description: "This is the PostgreSQL image name requested to deploy."
    value: "registry.access.redhat.com/cloudforms45/cfme-openshift-postgresql"
--
    name: "MEMCACHED_IMG_NAME"
    displayName: "Memcached Image Name"
    description: "This is the Memcached image name requested to deploy."
    value: "registry.access.redhat.com/cloudforms45/cfme-openshift-memcached"
--
    name: "APPLICATION_IMG_NAME"
    displayName: "Application Image Name"
    description: "This is the Application image name requested to deploy."
    value: "registry.access.redhat.com/cloudforms45/cfme-openshift-app"

Comment 7 errata-xmlrpc 2017-08-16 07:59:16 UTC
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:2482