Bug 1466770 - [3.4] Running the config.yml playbook fails on the second run
[3.4] Running the config.yml playbook fails on the second run
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: 3.4.z
Assigned To: Russell Teague
Gan Huang
Depends On:
  Show dependency treegraph
Reported: 2017-06-30 08:18 EDT by Russell Teague
Modified: 2017-07-27 14:02 EDT (History)
11 users (show)

See Also:
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'.
Story Points: ---
Clone Of: 1443416
Last Closed: 2017-07-27 14:02:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1810 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-07-27 17:58:37 EDT

  None (edit)
Comment 1 Russell Teague 2017-06-30 08:21:08 EDT
Proposed: https://github.com/openshift/openshift-ansible/pull/4650
Comment 4 Gan Huang 2017-07-06 03:32:11 EDT
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-09 22:31:41 EDT
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 14:02:01 EDT
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.


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