Bug 1651227

Summary:	[downstream clone - 4.2.8] Require Ansible 2.7.2+
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	RHV bug bot <rhv-bugzilla-bot>
Component:	ovirt-ansible-roles	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED ERRATA	QA Contact:	Pavel Novotny <pnovotny>
Severity:	unspecified	Docs Contact:	Rolfe Dlugy-Hegwer <rdlugyhe>
Priority:	unspecified
Version:	unspecified	CC:	bugs, cshao, mgoldboi, mperina, rdlugyhe
Target Milestone:	ovirt-4.2.8	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.8.2	Doc Type:	Release Note
Doc Text:	Ansible 2.7.2 or higher is required to run oVirt Ansible roles.	Story Points:	---
Clone Of:	1651220	Environment:
Last Closed:	2019-01-22 12:45:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1651220
Bug Blocks:

Description RHV bug bot 2018-11-19 13:30:27 UTC

+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1651220 +++
======================================================================

Ansible 2.7.2 or higher is required to execute oVirt Ansible roles. This bump will allow us to remove all modules updates from 2.5 to 2.7.2, which were part of our roles.

(Originally by Martin Perina)

Comment 4 Pavel Novotny 2019-01-03 17:11:28 UTC

FailedQA in ovirt-engine-4.2.8.1-0.1.el7ev.noarch

# rpm -qR ovirt-engine | grep ansible
ansible >= 2.5
ovirt-ansible-roles >= 1.1.2

Looks like the patch #96285 didn't make it to the latest 4.2.8 RHV build (4.2.8-2).
The patch was merged on December 18th while QA got the latest RHV 4.2.8 on December 13th.

Comment 5 Pavel Novotny 2019-01-10 18:10:29 UTC

Verified in ovirt-engine-4.2.8.2-0.1.el7ev.noarch

# rpm -qR ovirt-engine | grep ^ansible
ansible >= 2.7.2

Comment 7 errata-xmlrpc 2019-01-22 12:45:08 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:0122