Created from redmine issue http://projects.theforeman.org/issues/16789

Upstream bug assigned to inecas@redhat.com

Verified with Satellite 6.4.0 snap11.

I can see ansible related installer options in satellite installer:

~]# satellite-installer --help | grep ansible
    --[no-]enable-foreman-plugin-ansible Enable 'foreman_plugin_ansible' puppet module (default: true)
    --[no-]enable-foreman-proxy-plugin-ansible Enable 'foreman_proxy_plugin_ansible' puppet module (default: true)
= Module foreman_proxy_plugin_ansible:


Also can see ansible feature enabled on smart-proxy. Changes on filesystem can be seen with following:

~]# cat /usr/share/foreman-installer/modules/foreman_proxy/manifests/plugin/ansible/params.pp
# Ansible proxy default parameters
class foreman_proxy::plugin::ansible::params {
  $enabled     = true
  $listen_on   = 'https'
  $ansible_dir = '/usr/share/foreman-proxy'
  $working_dir = '/tmp'
  $host_key_checking = false
}


@Ivan: Could you please take a look and suggest if anything specific we should test for this RFE ?

I confirm the verification steps are appropriate for this BZ.

Thanks Ivan. Moving this to verified

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-2018:2927