Bug 1387298

Summary: Install python ansible callback module using the installer
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: AnsibleAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: high    
Version: 6.3.0CC: dlobatog, ehelms, mhulan, ohadlevy, sghai, sthirugn
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 19:18:16 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:

Description sthirugn@redhat.com 2016-10-20 14:51:29 UTC
Description of problem:


Version-Release number of selected component (if applicable):
Satellite-6.3.0-Snap 5

How reproducible:
Always

Steps to Reproduce:
1. After installing the ansible plugin, the user has to manually pull the ansible callback python module to set it up in Satellite6: (see https://theforeman.org/plugins/foreman_ansible/0.x/index.html#2.1Ansiblecallback):

# wget https://raw.githubusercontent.com/theforeman/foreman_ansible/master/extras/foreman_callback.py -O ~/.ansible/plugins/callback_plugins/foreman_callback.py

Actual results:
1. User has to manually wget the above python module.
2. the module exists in github

Expected results:
1. Package the python module in Satellite repo
2. Install the python module in Satellite when I install the Ansible plugin.

Additional info:

Comment 2 Ohad Levy 2016-10-26 10:14:26 UTC
where would that be installed into? I don't think its obvious that a user will use ansible on the satellite server it self?

FYI - it has been merged into ansible upstream (https://github.com/ansible/ansible/pull/17141) and would be available in some future release of ansible as well.

I would prefer to leave it as a documentation exercise, as it greatly depends on a user ansible current environment

Comment 3 sthirugn@redhat.com 2017-01-05 19:09:09 UTC
(In reply to Ohad Levy from comment #2)
> where would that be installed into? I don't think its obvious that a user
> will use ansible on the satellite server it self?
> 
> FYI - it has been merged into ansible upstream
> (https://github.com/ansible/ansible/pull/17141) and would be available in
> some future release of ansible as well.
> 
> I would prefer to leave it as a documentation exercise, as it greatly
> depends on a user ansible current environment

I agree with your explanation.

I asked two things in the bug:
1. Package the python module in Satellite repo 
   - this question is still open.
2. Install the python module in Satellite when I install the Ansible plugin.     - you answered this in Comment 2

Comment 4 Daniel Lobato Garcia 2017-01-26 16:24:22 UTC
Ansible upstream now serves the callback, so we don't need to package the python module anymore.

In addition to that the installer module will configure it: https://github.com/theforeman/puppet-foreman_proxy/pull/315

Closing as POST those changes were merged upstream some time ago.

Comment 5 sthirugn@redhat.com 2017-03-07 16:04:11 UTC
This will be tested once this fix lands in a downstream snap for sat 6.3

Comment 9 Jameer Pathan 2018-09-21 15:11:38 UTC
Needinfo

@satellite 6.4.0 snap22
ansible-2.6.3-1.el7ae.noarch

1. Ansible upstream now serves the callback

2. installer module configures it
 
3. i am able to generate report and facts with the callback installed on to ~foreman-proxy/.ansible.cfg

is above mentioned points are enough to verify this bug,
or there is anything else i need to do.

Comment 10 Marek Hulan 2018-09-21 16:02:01 UTC
Yes, that's it

Comment 11 Bryan Kearney 2018-10-16 19:18:16 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