-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.12.0
-
False
-
-
False
-
CLOSED
-
800
-
Platform
-
-
-
Moderate
-
None
Description of problem:
It's possible to enable the ansible feature using "-enable-foreman-proxy-plugin-ansible" option with satellite-installer for an external capsule but we cannot disable it back using "-no-enable-foreman-proxy-plugin-ansible".
It happens as, While enabling the feature, the Installer creates this file on the capsule as expected i.e.
- cat /etc/foreman-proxy/settings.d/ansible.yml
—
:enabled: https
:ansible_dir: /usr/share/foreman-proxy
:working_dir: /tmp
but when we use "-no-enable-foreman-proxy-plugin-ansible" or "-foreman-proxy-plugin-ansible-enabled false" , The installer does not touches that file or removes it.
Due to the same, even if we can see the following in capsule-answers file i.e.
- grep ansible /etc/foreman-installer/scenarios.d/capsule-answers.yaml
enable_ansible: true
foreman_proxy::plugin::ansible: false
Due to the presence of /etc/foreman-proxy/settings.d/ansible.yml, smaprt-proxy will always think that the feature is enabled.
Version-Release number of selected component (if applicable):
Satellite Capsule 6.12
How reproducible:
Always
Steps to Reproduce:
1. Install a Satellite and an external capsule 6.12
2. Note that by default the external capsule does not have Ansible feature enabled.
3. And there is no /etc/foreman-proxy/settings.d/ansible.yml file present.
4. Enable the ansible feature on the capsule by following https://access.redhat.com/solutions/5506051
5. Now, Try disabling it using :
- satellite-installer --no-enable-foreman-proxy-plugin-ansible && satellite-maintain service restart
or,
- satellite-installer --foreman-proxy-plugin-ansible-enabled false && satellite-maintain service restart
6. Check back if the file /etc/foreman-proxy/settings.d/ansible.yml exists on the capsule or not.
7. Refresh and Check the capsule features from Infrastructure --> Capsules page and noticed the "Ansible" feature there
Actual results:
The file /etc/foreman-proxy/settings.d/ansible.yml once created, will always be present and the Ansible feature cannot be disabled.
Expected results:
The ansible feature should be disabled properly.
Additional info:
WORKAROUND:
- mv /etc/foreman-proxy/settings.d/ansible.yml /tmp/
- systemctl restart foreman-proxy