Bug 1538807 – [3.7] Installer terminates after single node reports error despite error tolerance

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1538807 - [3.7] Installer terminates after single node reports error despite error tolerance

Summary:	[3.7] Installer terminates after single node reports error despite error tole...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Upgrade (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	high Severity low
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	Russell Teague
QA Contact:	Weihua Meng
Docs Contact:

URL:
Whiteboard:
Keywords:	DeliveryBlocker

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-25 16:38 EST by Russell Teague
Modified:	2018-04-05 05:36 EDT (History)
CC List:	6 users (show)

See Also:
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 05:36:18 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0636	None	None	None	2018-04-05 05:36 EDT

Groups: None (edit)

Comment 2 Weihua Meng 2018-01-25 20:29:07 EST

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."

Comment 3 Scott Dodson 2018-01-26 15:01:40 EST

(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.

Comment 4 Weihua Meng 2018-01-28 00:59:42 EST

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

Comment 8 errata-xmlrpc 2018-04-05 05:36:18 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.

https://access.redhat.com/errata/RHBA-2018:0636

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