Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1450415

Summary: [3.3] Installing containerized using the 3.3 playbooks may install other versions
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.3.1CC: aos-bugs, jchaloup, jialiu, jkaur, jokerman, mmccomas, sdodson
Target Milestone: ---   
Target Release: 3.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When performing a containerized installation without setting openshift_image_tag the latest image was used to determine the correct version of the product to install. The latest tag may point at different releases based on whichever version was pushed most recently. Because of this we've modified the installer to default to the 'v3.3' tag when running the 3.3 installer so that we're sure to get the latest v3.3 release.
Story Points: ---
Clone Of: 1450412 Environment:
Last Closed: 2017-05-17 17:42:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1448842, 1450412    
Bug Blocks:    

Comment 3 Wenkai Shi 2017-05-15 09:48:04 UTC
Seems typo error:

# rpm -q atomic-openshift-utils
atomic-openshift-utils-3.3.81-1.git.0.60b41c9.el7.noarch
]# vim /usr/share/ansible/openshift-ansible/roles/openshift_version/tasks/set_version_containerized.yml
...
- name: Set default image tag based on OCP versus origin
  set_fact:
    l_image_tag: "{{ 'v3.4' if openshift.common.deployment_type == 'openshift-enterprise' else 'latest' }}"
...

Comment 6 Wenkai Shi 2017-05-16 02:39:45 UTC
Verified with version atomic-openshift-utils-3.3.82-1.git.0.af0c922.el7, installation succeed with correct tag.

Comment 8 errata-xmlrpc 2017-05-17 17:42:43 UTC
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:1244