Bug 1759143

Summary:	[RFE] Use ansible-runner-service instead of ansible-playbook to execute Ansible playbooks from engine
Product:	[oVirt] ovirt-engine	Reporter:	Martin Perina <mperina>
Component:	BLL.Infra	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.0	CC:	bugs, emarcus, omachace, pelauter
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+ pmatyas: testing_plan_complete+ pelauter: planning_ack+ mperina: 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:04:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Perina 2019-10-07 13:23:44 UTC

At the moment we are using ansible-playbook command to execute Ansible playbooks from ovirt-engine, but this approach has several issues:

1. Lack of detailed progress report from running playbooks
2. Lack of detailed logs if playbook needs to return any data back to engine

We are going to use ansible-runner-service instead of ansible-playbook to fix all issues above.

Comment 4 Petr Matyáš 2020-01-20 15:38:37 UTC

Verified on ovirt-engine-4.4.0-0.14.master.el7.noarch

Comment 5 Sandro Bonazzola 2020-05-20 20:04:22 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.