Red Hat Bugzilla – Bug 1421982
php latest tag points to different version between image-streams-centos7.json and image-streams-rhel7.json
Last modified: 2017-08-16 15:51 EDT
Description of problem: PHP latest tag points to 7.0 in image-streams-centos7.json [1], but points to 5.6 in image-streams-rhel7.json [2]. [1] https://github.com/hhorak/origin/blob/97c1fe5c0dccf0983f19a100f05471dff627a135/examples/image-streams/image-streams-centos7.json#L244 [2] https://github.com/hhorak/origin/blob/97c1fe5c0dccf0983f19a100f05471dff627a135/examples/image-streams/image-streams-rhel7.json#L244 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: PHP latest tag points to 7.0 in image-streams-centos7.json, but points to 5.6 in image-streams-rhel7.json. Expected results: Both of them should point to 7.0 Additional info:
This issue has been fixed in origin by Ben, just keep track it to verify in OCP later.
How can we know if this is in OCP? Is there a pull request, or something else, to let us know? Or can someone verify if it's in there already.
It would be here, i think: https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/v1.5/image-streams/image-streams-rhel7.json#L233-L245 since it's not, it means someone still needs to run the ansible sync script that updates ansible w/ the latest template/imagestream files. i'll do it here: https://github.com/openshift/openshift-ansible/pull/3386
Verified with this version: openshift v3.6.88 7.0 (latest) tagged from registry.access.redhat.com/rhscl/php-70-rhel7:latest Build and run PHP 7.0 applications on RHEL 7. For more information about using this builder image, including OpenShift considerations, see https://github.com/sclorg/s2i-php-container/blob/master/7.0/README.md. Tags: builder, php Supports: php:7.0, php Example Repo: https://github.com/openshift/cakephp-ex.git * registry.access.redhat.com/rhscl/php-70-rhel7@sha256:6056c56f28e11fb04895b1931eb84a5ae6dd5175d06b25d1186cd21387adf241 4 days ago
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/RHEA-2017:1716