+++ This bug was initially created as a clone of Bug #1484398 +++ Description of problem: Users always have to provide the IMAGE_VERSION=3.3.1 param when running the deployer or else they will get the latest 3.3.0 version instead of the 3.3.1 version. Version-Release number of selected component (if applicable): OpenShift 3.3.x OpenShift 3.4.x How reproducible: Always Steps to Reproduce: 1. Install logging using the deployer $ oc new-app logging-deployer-template Actual results: $ oc exec logging-es-ja0vy5bi-1-8c9v6 -- ls -la /root/buildinfo Dockerfile-openshift3-logging-elasticsearch-3.3.0-11 Expected results: $ oc exec logging-es-ja0vy5bi-1-8c9v6 -- ls -la /root/buildinfo Dockerfile-openshift3-logging-elasticsearch-3.3.1-17 Additional info: Users need to run the deployer like so: $ oc new-app logging-deployer-template --param IMAGE_VERSION=3.3.1
https://github.com/openshift/openshift-ansible/pull/5173
Build openshift-ansible-3.3.119-1.git.0.2872586.el7 is not pushed to puddle server, will verify it after we get the build
Used build openshift-ansible-3.3.119-1.git.0.2872586.el7 from https://errata.devel.redhat.com/advisory/29863 to build env, deployed metrics and logging with v3.3 image tag, we could get the latest 3.3.1 images, and they passed our sanity testing. take metrics-heapster for example, the image vesion is metrics-heapster-3.3.1-24 # oc exec heapster-51xtv -- ls -al /root/buildinfo total 12 drwxr-xr-x. 2 root root 90 Aug 21 17:20 . dr-xr-x---. 3 root root 4096 Jul 25 22:00 .. -rw-r--r--. 1 root root 1959 Aug 21 17:18 Dockerfile-openshift3-metrics-heapster-3.3.1-24 -rw-r--r--. 1 root root 2708 Jul 25 21:59 Dockerfile-rhel7-7.4-81 metrics-heapster-3.3.1-24 is the currently latest image, metrics-heapster-3.3.1-24 and metrics-heapster:v3.3 are the same version openshift3/metrics-heapster 3.3.1-24 56b6d60201f6 8 days ago 281.1 MB openshift3/metrics-heapster v3.3 56b6d60201f6 8 days ago 281.1 MB # openshift version openshift v3.3.1.46.11 kubernetes v1.3.0+52492b4 etcd 2.3.0+git
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:2639