Bug 1566838 - The 3.5.0 is not point to the latest v3.5 logging images
Summary: The 3.5.0 is not point to the latest v3.5 logging images
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-13 05:54 UTC by Anping Li
Modified: 2018-09-19 12:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-19 12:31:30 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Anping Li 2018-04-13 05:54:08 UTC
Description of problem:
The 3.5.0 is the default tag for all logging images in openshift-ansible.  The 3.5.0 is not point to the latest v3.5 logging images in registry.access.redhat.com.  This will result in older version when install/re-deploy logging with default image version (without openshift_logging_image_version=v3.5).

The workaround is specified the openshift_logging_image_version=v3.5 in inventory


In openshift ansible 3.5.164 , the default image tag is 3.5.0.
# cat /usr/share/ansible/openshift-ansible/roles/openshift_logging/vars/openshift-enterprise.yml
---
__openshift_logging_image_prefix: "{{ openshift_hosted_logging_deployer_prefix | default('registry.access.redhat.com/openshift3/') }}"
__openshift_logging_image_version: "{{ openshift_hosted_logging_deployer_version | default ('3.5.0') }}"


In registry.access.redhat.com, the 3.5.0 isn't link to the latest image v3.5.
registry.access.redhat.com/openshift3/logging-fluentd                             3.5.0               91f5c53198d2        4 months ago        236 MB
registry.access.redhat.com/openshift3/logging-fluentd                             v3.5                6e1f4c341bf9        3 days ago          236.1 MB



[anli@upg_slave_qeos10 images]$ sh getrelease 3.5 blogging 
--> Checking openshift3/logging-kibana:v3.5
---->image for openshift3/logging-kibana:v3.5 found
    "v3.5": "d54432e6fc63a59a00caec2e6bc8508527f30ddbadb779cdd68ed701c6bdef36",
    "v3.5.5.31.66": "d54432e6fc63a59a00caec2e6bc8508527f30ddbadb779cdd68ed701c6bdef36",
    "v3.5.5.31.66-55": "d54432e6fc63a59a00caec2e6bc8508527f30ddbadb779cdd68ed701c6bdef36",


[anli@upg_slave_qeos10 images]$ sh getrelease 3.5.0 blogging 
--> Checking openshift3/logging-kibana:3.5.0
---->image for openshift3/logging-kibana:3.5.0 found
    "3.5.0": "b65c339eb8bdddf07482fe5b2d70fd0bd93ee128dffab813ed702709d1606d12",
    "3.5.0-54": "b65c339eb8bdddf07482fe5b2d70fd0bd93ee128dffab813ed702709d1606d12",



Version-Release number of selected component (if applicable):
openshift-ansible-3.5.164
registry.access.redhat.com/openshift3/logging* images

How reproducible:
always

Steps to Reproduce:
1. Don't specify the inventory variable 'openshift_logging_image_version' and deploy logging
#openshift_logging_image_version=v3.5
openshift_logging_image_prefix=registry.access.redhat.com/openshift3/
openshift_logging_install_logging=true

Actual Result:
The logging are not install/upgrade to latest version v3.5.


Expected Result:
The logging are install/upgrade to latest version v3.5.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.