Red Hat Bugzilla – Bug 1500364
mariadb, postgresql, mysql, and mediawiki APBs should use rhcc images
Last modified: 2017-12-07 02:12:13 EST
Description of problem: Ansible Playbook Bundles that are to be shipped as part of OpenShift should use rhcc images in both the playbooks and apb.yml (dependencies). How reproducible: Always Steps to Reproduce: For each of (mariadb, postgresql, mysql, and mediawiki)-apb 1. docker pull registry.access.redhat.com/openshift3/${apb-name}-apb 2. docker inspect registry.access.redhat.com/openshift3/${apb-name}-apb --format "{{ index .Config.Labels \"com.redhat.apb.spec\" }}" | base64 --decode Expected results: All APBs should reference registry.access.redhat.com/(rhscl|openshift3)/ images.
https://github.com/ansibleplaybookbundle/rhscl-mariadb-apb/pull/5 https://github.com/ansibleplaybookbundle/rhscl-postgresql-apb/pull/6 https://github.com/ansibleplaybookbundle/rhscl-mysql-apb/pull/5 https://github.com/ansibleplaybookbundle/mediawiki123-apb/pull/9
All four 3.7 latest images look good. For dependencies: openshift3/mediawiki-apb:v3.7.4-2 registry.access.redhat.com/openshift3/mediawiki-123:latest openshift3/mariadb-apb:v3.7.4-2 registry.access.redhat.com/rhscl/mariadb-100-rhel7 registry.access.redhat.com/rhscl/mariadb-101-rhel7 openshift3/mysql-apb:v3.7.4-2 registry.access.redhat.com/rhscl/mysql-56-rhel7 registry.access.redhat.com/rhscl/mysql-57-rhel7 openshift3/postgresql-apb:v3.7.4-2 registry.access.redhat.com/rhscl/postgresql-94-rhel7 registry.access.redhat.com/rhscl/postgresql-95-rhel7 For 3.6, we only deliver openshift3/mediawiki-apb and openshift3/postgresql-apb, they are not updated for 3 months, do not contain the new code. If this is must for tag 3.6 apb images, we need to build new images for those two. If not, All look good for me.
Agree with Weihua/Xialoi, this was intended for 3.7.0 and not 3.6.z
Verified with latest apb v3.7 images(v3.7.4-2).
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/RHSA-2017:3389