Description of problem: We need to switch to use ansible-runner for provider operations, which is the Ansible recommended way.
https://github.com/ManageIQ/manageiq/pull/17688
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/e214bf26f7237e2a1c5465b7eeb65ee04e4db18e commit e214bf26f7237e2a1c5465b7eeb65ee04e4db18e Author: Ladislav Smola <lsmola> AuthorDate: Tue Jul 10 11:26:25 2018 -0400 Commit: Ladislav Smola <lsmola> CommitDate: Tue Jul 10 11:26:25 2018 -0400 Use ansible-runner instead of ansible-playbook Use ansible-runner instead of ansible-playbook Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1599798 lib/ansible/runner.rb | 16 +- 1 file changed, 14 insertions(+), 2 deletions(-)
ansible runner merged to appliance repo, moving to POST
According to Ladas the use case of bug 1644605 should be enough to verify this RFE. Moving to Verified based on the verification of bug 1644605.
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/RHSA-2019:0212