| Summary: | [RFE] Add ansible-related installer migrations to katello-installer | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Ivan Necas <inecas> |
| Component: | Installer | Assignee: | Ivan Necas <inecas> |
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2.0 | CC: | bkearney, cwelton, ehelms, inecas, jcallaha |
| Target Milestone: | 6.4.0 | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-16 15:26:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ivan Necas
2016-10-19 19:20:43 UTC
Created from redmine issue http://projects.theforeman.org/issues/16789 Upstream bug assigned to inecas 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 |