Bug 1726037

Summary: Add roles_path to ansible.cfg
Product: Red Hat Satellite Reporter: Ondřej Pražák <oprazak>
Component: InstallerAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Devendra Singh <desingh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: egolov, rbertolj
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-installer-1.22.0.10 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:51:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ondřej Pražák 2019-07-02 06:21:46 UTC
We should add roles_path to ansible.cfg so that smart proxy knows where to import roles from.

Comment 3 Ondřej Pražák 2019-07-02 06:31:49 UTC
*** Bug 1726042 has been marked as a duplicate of this bug. ***

Comment 4 Ondřej Pražák 2019-07-02 06:32:08 UTC
*** Bug 1726040 has been marked as a duplicate of this bug. ***

Comment 5 Bryan Kearney 2019-07-02 08:02:46 UTC
Upstream bug assigned to oprazak

Comment 6 Bryan Kearney 2019-07-02 08:02:47 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27196 has been resolved.

Comment 7 Devendra Singh 2019-08-30 13:32:43 UTC
This bug has verified in 6.6.0 Snap17.

Below points cover in the verification

* Import operation working properly from Satellite and from the Capsule.
   theforeman.foreman_scap_client roles imported successfully.

* Verified the path existence of  /usr/share/ansible/roles in /usr/share/foreman-proxy/.ansible.cfg file.
# grep -i roles_path /usr/share/foreman-proxy/.ansible.cfg
roles_path = /etc/ansible/roles:/usr/share/ansible/roles

* # rpm -q foreman-installer
foreman-installer-1.22.0.10-1.el7sat.noarch

Comment 10 Bryan Kearney 2019-10-22 19:51:49 UTC
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-2019:3172