Description of problem: Currently, our sample APBs use registry.access.redhat.com for the application image's URL. See https://github.com/ansibleplaybookbundle/postgresql-apb/blob/8bc1a957f5784b619bcde56b3cd9052c4b035205/defaults/main.yml#L9 https://github.com/ansibleplaybookbundle/mysql-apb/blob/1a53adeae43c5ffcbf5577d504286c578407297c/defaults/main.yml#L12 https://github.com/ansibleplaybookbundle/mariadb-apb/blob/fda06b7c5c322b1ee735358d3d948bdf9744d510/defaults/main.yml#L9 https://github.com/ansibleplaybookbundle/mediawiki-apb/blob/cfd8427bad0fb1ed4ee73ef71e74fa5092afc979/downstream.patch#L10 These should be updated to point to 'registry.redhat.io'. Additionally, for the purposes of development/testing, there should be a mechanism for overriding the registry URL used for the application image. For example, to use 'registry.dev.redhat.io' or 'registry.stage.redhat.io' instead of the production registry. How reproducible: Always Steps to Reproduce: 1. Start with an OpenShift Origin cluster w/ Service Catalog and Ansible Service Broker 2. Provision (postgresql-apb|mysql-apb|mariadb-apb|mediawiki-apb) 3. Verify deployed application's container image Actual results: Depending on the APB selected and the specific version you will see something of the form registry.access.redhat.com/rhscl/postgresql-96-rhel7 Expected results: Depending on the APB selected and the specific version you should see something of the form registry.redhat.io/rhscl/postgresql-96-rhel7
https://github.com/ansibleplaybookbundle/postgresql-apb/pull/56 https://github.com/ansibleplaybookbundle/mediawiki-apb/pull/40 https://github.com/ansibleplaybookbundle/mariadb-apb/pull/38 https://github.com/ansibleplaybookbundle/mysql-apb/pull/40
@David, I noticed the default dependence have been changed to production registry in latest downstream apb images. Could you provide the detail steps about how to override the registry_url?
Turns out, I simply forgot to update the labels on the respective Dockerfiles (where the base64 encoded apb.yml lives) downstream. The following images have the updated labels. openshift-enterprise-mariadb-apb-v3.11.0-0.11.0.2 openshift-enterprise-mediawiki-apb-v3.11.0-0.11.0.2 openshift-enterprise-postgresql-apb-v3.11.0-0.11.0.2 openshift-enterprise-mysql-apb-v3.11.0-0.11.0.2
That was silly of me. I mistakenly made the labels on those images "com.redhat.com.apb.spec" instead of "com.redhat.apb.spec". Fixing now.
For real this time: openshift-enterprise-mariadb-apb-v3.11.0-0.13.0.1 openshift-enterprise-mediawiki-apb-v3.11.0-0.13.0.1 openshift-enterprise-postgresql-apb-v3.11.0-0.13.0.1 openshift-enterprise-mysql-apb-v3.11.0-0.13.0.1
Errata https://errata.devel.redhat.com/brew/save_builds/33505 updated: openshift-enterprise-mariadb-apb-v3.11.0-0.13.0.1 openshift-enterprise-mediawiki-apb-v3.11.0-0.13.0.1 openshift-enterprise-postgresql-apb-v3.11.0-0.13.0.1 openshift-enterprise-mysql-apb-v3.11.0-0.13.0.1 openshift-enterprise-asb-container-v3.11.0-0.13.0.1
Not sure how I keep messing up the metadata, but the encoded spec didn't match the apb.yml that is on the branch. Updated.
Test passed and changing to verified # oc get bundles -o yaml | grep metadata.*console metadata: '{"console.openshift.io/iconClass":"icon-mediawiki","dependencies":["registry.redhat.io/openshift3/mediawiki:latest"],"displayName":"Mediawiki metadata: '{"console.openshift.io/iconClass":"icon-mysql-database","dependencies":["registry.redhat.io/rhscl/mysql-56-rhel7","registry.redhat.io/rhscl/mysql-57-rhel7"],"displayName":"MySQL metadata: '{"console.openshift.io/iconClass":"icon-mariadb","dependencies":["registry.redhat.io/rhscl/mariadb-100-rhel7","registry.redhat.io/rhscl/mariadb-101-rhel7","registry.redhat.io/rhscl/mariadb-102-rhel7"],"displayName":"MariaDB metadata: '{"console.openshift.io/iconClass":"icon-postgresql","dependencies":["registry.redhat.io/rhscl/postgresql-94-rhel7","registry.redhat.io/rhscl/postgresql-95-rhel7","registry.redhat.io/rhscl/postgresql-96-rhel7"],"displayName":"PostgreSQL # oc get clusterserviceclass -o yaml | grep -E "\/mysql|\/postgresql|\/mediawiki|\/mariadb" | grep -v document - registry.redhat.io/openshift3/mediawiki:latest - registry.redhat.io/rhscl/mysql-56-rhel7 - registry.redhat.io/rhscl/mysql-57-rhel7 - registry.redhat.io/rhscl/mariadb-100-rhel7 - registry.redhat.io/rhscl/mariadb-101-rhel7 - registry.redhat.io/rhscl/mariadb-102-rhel7 - registry.redhat.io/rhscl/postgresql-94-rhel7 - registry.redhat.io/rhscl/postgresql-95-rhel7 - registry.redhat.io/rhscl/postgresql-96-rhel7
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-2018:2652