Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1740842

Summary:	Validate Ansible 2.8 with openshift-ansible 3.11
Product:	OpenShift Container Platform	Reporter:	Russell Teague <rteague>
Component:	Installer	Assignee:	Russell Teague <rteague>
Installer sub component:	openshift-ansible	QA Contact:	Weihua Meng <wmeng>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	rsandu, wmeng
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Support Ansible 2.8+ Reason: Older versions of Ansible will be unsupported and latest versions include security fixes Result: OpenShift-Ansible playbooks complete successfully when using Ansible 2.8+	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-03 15:56:03 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:

Description Russell Teague 2019-08-13 17:35:45 UTC

Description of problem:
OpenShift-Ansible 3.11 (openshift-ansible-3.11.135 or later) should support using Ansible 2.8.

Code refactoring was initially implemented in PR#11325 with several follow-up fixes.

https://github.com/openshift/openshift-ansible/pull/11325


Acceptance Criteria
----------------------------
No regressions observed when running supported playbooks with Ansible 2.8

Comment 1 Weihua Meng 2019-08-14 08:44:37 UTC

Install success, 
openshift-ansible-3.11.136-1.git.0.b757272.el7

ansible-2.8.3-1.el7ae
and
ansible-2.6.18-1.el7ae

Comment 3 Weihua Meng 2019-08-26 07:50:30 UTC

Fixed. 

Install success, 
openshift-ansible-3.11.141-1.git.0.a7e91cd.el7

ansible-2.8.4-1.el7ae
and
ansible-2.6.19-1.el7ae

Comment 5 errata-xmlrpc 2019-09-03 15:56:03 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-2019:2580