Bug 1538807
Summary: | [3.7] Installer terminates after single node reports error despite error tolerance | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Russell Teague <rteague> |
Component: | Cluster Version Operator | Assignee: | Russell Teague <rteague> |
Status: | CLOSED ERRATA | QA Contact: | Weihua Meng <wmeng> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 3.7.0 | CC: | aos-bugs, jialiu, jokerman, jupierce, mmccomas, wmeng |
Target Milestone: | --- | Keywords: | DeliveryBlocker |
Target Release: | 3.7.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Incorrect batch size calculations in Ansible 2.4.1 would cause playbooks to fail when using max_fail_percentage. The batch calculations were updated in Ansible 2.4.2 to correctly account for failures in each batch.
|
Story Points: | --- |
Clone Of: | 1504075 | Environment: | |
Last Closed: | 2018-04-05 09:36:18 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 2
Weihua Meng
2018-01-26 01:29:07 UTC
(In reply to Weihua Meng from comment #2) > ansible 2.4.2 is expected in OCP 3.7 repo, according to "use latest ansible > in OpenShift puddle now until we are notified that we will no longer ship > ansible in OpenShift anymore." We haven't shipped ansible 2.4 in any OCP repos prior to OCP 3.9. It's been shipped via RHEL Extras which just shipped 2.4.2.0 yesterday. Fixed as ansible 2.4.2 is in rhel-7-server-extras-rpms and right ansible version should be used according to openshift official doc https://docs.openshift.com/container-platform/3.7/install_config/upgrading/automated_upgrades.html If you are upgrading from OpenShift Container Platform 3.6 to 3.7, manually disable the 3.6 channel and enable the 3.7 channel on each master and node host: # subscription-manager repos --disable="rhel-7-server-ose-3.6-rpms" \ --enable="rhel-7-server-ose-3.7-rpms" \ --enable="rhel-7-server-extras-rpms" \ --enable="rhel-7-fast-datapath-rpms" # yum clean all 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-2018:0636 |