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

Bug 1762263

Summary:	[RFE] Require Ansible 2.9 in ovirt-engine-metrics
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Martin Perina <mperina>
Component:	Generic	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bugs
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature
Target Release:	---	Flags:	mperina: ovirt-4.4? mperina: planning_ack? sradco: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:01:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Perina 2019-10-16 10:54:50 UTC

Currently ovirt-engine-metrics requires Ansible >= 2.8.3, but there are many fixes in oVirt Ansible modules and Ansible itself in 2.8/2.9 versions, so we would like to require Ansible 2.9.0 in oVirt engine 4.4. This RFE contains following work:

1. Bump requirement to Ansible >= 2.9.0
2. Remove all updated modules included within ovirt-engine-metrics playbooks/roles projects which are fixed in Ansible 2.9
3. Align ovirt-engine-metrics playbooks/roles with Ansible 2.9 recommendation (for example remove all usage of deprecated code)

Comment 1 Guilherme Santos 2020-02-13 13:57:50 UTC

Verified with:
ovirt-engine-metrics-1.3.6.4-1.el7ev

Steps:
1. In a fresh machine run: # yum install ovirt-engine-metrics

Results:
yum requires Ansible-2.9.4-1.el7ae as dependency

Comment 2 Sandro Bonazzola 2020-05-20 20:01:58 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.