Bug 1786358
| Summary: | [RFE] Ability to make persistent changes in "ansible.cfg" on Satellite Server. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Karan Kohli <kkohli> |
| Component: | Ansible - Configuration Management | Assignee: | Adam Ruzicka <aruzicka> |
| Status: | CLOSED ERRATA | QA Contact: | Shweta Singh <shwsingh> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.6.0 | CC: | addubey, ahumbe, akapse, aruzicka, ben.formosa, casmith, ehelms, eric.nothen, gardar.arnarsson, gtalreja, hakon.gislason, jpathan, kkinge, ktordeur, musman, nikhjain, oezr, pcreech, pwaghmar, rlavi, ryp, sadas, shwsingh, zhunting, zuansorg |
| Target Milestone: | 6.13.0 | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-smart_proxy_ansible-3.5.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-03 13:20:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Can this be remade as an RFE? This is currently working as intended. What are you trying to do with the ansible.cfg? In my case, I am setting a vault_password_file parameter, but there's many other options that would fall on the same case as the hiera options are very limited right now. Also for /usr/share/foreman-proxy/.ansible.cfg when following instructions from https://access.redhat.com/solutions/4088231 With the increasing (and better) support for Ansible in Satellite, this becomes more important. Is there any movement on this? Verified. Version Tested: Satellite 6.13 Snap 4.0 Verification Steps: 1.Navigate to "/etc/ansible/ansible.cfg" and update the file with "local_tmp = /tmp". 2.Run "satellite-installer" command. 3.Verify that the changes persists post running above command. Result: Changes made to "/etc/ansible/ansible.cfg" are persistent. Note: Satellite 6.13 and above versions use ansible.cfg present in path "/etc/ansible/ansible.cfg". 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 (Important: Satellite 6.13 Release), 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-2023:2097 |
Description of problem: Custom changes made in "/etc/foreman-proxy/ansible.cfg" are removed after satellite installer is re-run. Version-Release number of selected component (if applicable): Satellite 6.6 How reproducible: 100% Steps to Reproduce: 1. Make custom changes in "/etc/foreman-proxy/ansible.cfg". 2. Run satellite installer or install/update packages using satellite- maintain(in which satellite installer is executed automatically) 3. All of the custom changes made in "/etc/foreman-proxy/ansible.cfg" file will be removed and the file will be restored to its default state. Actual results: The custom changes are removed. Expected results: The custom changes should not be removed. Additional info: ~~ Making changes in below file only make sure that when satellite-installer is re-run then custom changes in "/etc/foreman-proxy/ansible.cfg" file are not removed. >> /usr/share/foreman-installer/modules/foreman_proxy/templates/plugin/ansible.cfg.erb