Description of problem: On a freshly installed Satellite 6.13, /etc/foreman-proxy/ansible.cfg is not longer present and we still get to see a broken link for /usr/share/foreman-proxy/.ansible.cfg file. Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch rubygem-smart_proxy_ansible-3.5.0-1.el8sat.noarch How reproducible: Always Steps to Reproduce: 1. Install Satellite 6.13 2. Check inside /usr/share/foreman-proxy/ using "ls -la" Actual results: # ll /usr/share/foreman-proxy/ -a | grep "\.ansi" lrwxrwxrwx. 1 root root 30 Nov 11 17:42 .ansible -> /var/lib/foreman-proxy/ansible lrwxrwxrwx. 1 root root 30 Nov 11 17:42 .ansible.cfg -> /etc/foreman-proxy/ansible.cfg lrwxrwxrwx. 1 root root 37 Nov 11 17:42 .ansible_galaxy -> /var/lib/foreman-proxy/ansible_galaxy # ls -ld /var/lib/foreman-proxy/ansible /etc/foreman-proxy/ansible.cfg /var/lib/foreman-proxy/ansible_galaxy ls: cannot access '/etc/foreman-proxy/ansible.cfg': No such file or directory drwxr-xr-x. 2 foreman-proxy foreman-proxy 6 Nov 11 17:42 /var/lib/foreman-proxy/ansible drwxr-xr-x. 2 foreman-proxy foreman-proxy 6 Nov 11 17:42 /var/lib/foreman-proxy/ansible_galaxy Expected results: * No such broken links should be present in the product. Additional info:
Is there any user impact or broken workflows as a result of this behavior?
(In reply to Brad Buckingham from comment #1) > Is there any user impact or broken workflows as a result of this behavior? Not at all as long as someone does not decide to put an ansible.cfg manually inside the target location, which then will cause issues. I am aware of a discussion here in https://bugzilla.redhat.com/show_bug.cgi?id=2171849#c2 about it as well.
The question is how Ansible behaves if it finds a broken link. According to Ansible docs, it searches for ~/.ansible.cfg and if not found, then it goes for /etc/ansible/ansible.cfg. The ~/.ansible.cfg file is technically there, so is it possible that Ansible ignores /etc/ansible/ansible.cfg because it finds the broken link? IMHO, the test case used to verify https://bugzilla.redhat.com/show_bug.cgi?id=1786358#c16 only tested that the modification in the cfg is persistent, not that it's applied during Ansible execution in Satellite.
I'm asking about the broken link because of https://bugzilla.redhat.com/show_bug.cgi?id=2171849
Broken links are ignored, in 2171849 they don't have a broken link.