Bug 1466770 - [3.4] Running the config.yml playbook fails on the second run
Summary: [3.4] Running the config.yml playbook fails on the second run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.4.z
Assignee: Russell Teague
QA Contact: Gan Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-30 12:18 UTC by Russell Teague
Modified: 2017-07-27 18:02 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When openshift_image_tag is specified in an inventory as on 3.X instead of a full tag of 3.X.x.x, the evaluation of `openshift_image_tag >= LooseVersion('3.X.0.0')` would result in False. This caused the condition to be improperly applied to logic elsewhere in the code resulting in invalid evaluation of version specific facts. The version comparisons have been updated to compare against the terse minimum version of '3.X'.
Clone Of: 1443416
Environment:
Last Closed: 2017-07-27 18:02:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1810 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-07-27 21:58:37 UTC

Comment 1 Russell Teague 2017-06-30 12:21:08 UTC 
Proposed: https://github.com/openshift/openshift-ansible/pull/4650
Comment 4 Gan Huang 2017-07-06 07:32:11 UTC 
Could anyone answer https://bugzilla.redhat.com/show_bug.cgi?id=1443416#c11?

Should QE verify this bug by setting "openshift_image_tag=v3.4" which should not be a valid usage in QE's experiences?
Comment 6 Gan Huang 2017-07-10 02:31:41 UTC 
It's incorrect usage that setting "openshift_image_tag=v3.4" for OCP installation, instead, we should set precise image tag like "openshift_image_tag=v3.4.x.x". 

Move to "verified" now until someone corrects QE for the usage about this option.
Comment 8 errata-xmlrpc 2017-07-27 18:02:01 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/RHBA-2017:1810
Note You need to log in before you can comment on or make changes to this bug.