Bug 1568713

Summary: Automatically install the dependent plugins for the Ansible plugin
Product: Red Hat Satellite Reporter: Martin Korbel <mkorbel>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: NightlyCC: ehelms, jhutar
Target Milestone: 6.4.0Keywords: 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 18:54:01 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:
Bug Depends On:    
Bug Blocks: 1449011    

Description Martin Korbel 2018-04-18 07:20:41 UTC
Description of problem:
The Ansible plugin depend on Remote Execution plugin. 
If we don't have installed Remote Execution plugin, we don't get any warning and the ansible plugin does not work. 

Version-Release numbe

foreman-installer-1.18.0-0.develop.201804160328gitc9bede9.el7


How reproducible:
100%

Steps to Reproduce:
1. > foreman-installer --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible
2. import a role and run it

Actual results:
Failed to connect to the host via ssh: Could not create directory '/usr/share/foreman-proxy/.ssh'.

Expected results:
The foreman installer installs all required dependencies automatically.

Additional info:

Comment 1 Brad Buckingham 2018-04-20 14:40:11 UTC
This is needed to support the 6.4 feature.

Comment 2 Brad Buckingham 2018-04-20 14:42:29 UTC
Associating with feature tracker bug 1449011

Comment 4 Martin Korbel 2018-05-29 09:00:52 UTC
VERIFIED on snap_6.4.0_5.0

The Remote Execution plugin was installed automatically.

Comment 6 Bryan Kearney 2018-10-16 18:54:01 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-2018:2927