Bug 1466770
| Summary: | [3.4] Running the config.yml playbook fails on the second run | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Russell Teague <rteague> |
| Component: | Installer | Assignee: | Russell Teague <rteague> |
| Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | abutcher, aos-bugs, edwkim, eparis, jialiu, jokerman, jswensso, mmccomas, myllynen, rteague, trankin |
| Target Milestone: | --- | ||
| Target Release: | 3.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 | Environment: | |
| Last Closed: | 2017-07-27 18:02:01 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: | |||
|
Comment 1
Russell Teague
2017-06-30 12:21:08 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? 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. 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 |