Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1734808

Summary: [RFE] Make Ansible Runner the only way to run Ansible
Product: Red Hat Satellite Reporter: Marek Hulan <mhulan>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: bkearney, pcreech, sokeeffe, trichard
Target Milestone: 6.7.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_ansible-4.0.0 Doc Type: Enhancement
Doc Text:
For improved Ansible performance and stability, ansible-runner is now the only available Ansible implementation. The ansible-playbook implementation is no longer available.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:25:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marek Hulan 2019-07-31 14:00:18 UTC
This bug was initially created as a copy of Bug #1698176, that tracked adding a new setting so users could chose between ansible-runner and ansible-playbook implementations. This new RFE makes the ansible-runner the only available option.

Comment 3 Marek Hulan 2019-09-24 04:49:55 UTC
Created redmine issue https://projects.theforeman.org/issues/27922 from this bug

Comment 4 Lukas Pramuk 2020-02-06 13:31:18 UTC
VERIFIED.

@satellite-6.7.0-5.beta.el7sat.noarch
tfm-rubygem-foreman_ansible-4.0.3-1.el7sat.noarch

by the following manual steps:

1) Check for the settings (that present in Sat6.6)

Administer -> Settings -> Ansible 

Implementation for running Ansible: ansible-playbook     <- this is missing at Sat6.7

>>> user no longer can choose between 'ansible-playbook' and 'ansible-runner' 

2) Schedule Ansible REX command and while checking for processes running on satellite: 
# watch "ps -efH | grep -A4 [a]nsible"
foreman+  2667 15180  1 08:17 pts/5    00:00:00     /usr/bin/python2 /usr/bin/ansible-runner run /tmp/d20200206-15180-1pova5e -p playbook.yml
foreman+  2675  2667 23 08:17 pts/6    00:00:01       /usr/bin/python2 /usr/bin/ansible-playbook -i /tmp/d20200206-15180-1pova5e/inventory playbook.yml
foreman+  2723  2675  5 08:17 pts/6    00:00:00         /usr/bin/python2 /usr/bin/ansible-playbook -i /tmp/d20200206-15180-1pova5e/inventory playbook.yml
foreman+  2787  2723  1 08:17 pts/6    00:00:00           ssh -o ProxyCommand=none -o StrictHostKeyChecking=no -o Port=22 -o IdentityFile="/usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy"...

>>> the manadatory implementation 'ansible-runner' is always used

Comment 8 errata-xmlrpc 2020-04-14 13:25: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/RHSA-2020:1454