Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2016-10-11 13:09:44 UTC
Description of problem:
ansible playbook runs not reported to foreman while using ansible 2.x version
Version-Release number of selected component (if applicable):
# rpm -qa | grep foreman
tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch
tfm-rubygem-foreman_setup-5.0.0-1.fm1_13.el7.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch
foreman-debug-1.13.0-1.el7.noarch
foreman-proxy-1.13.0-1.el7.noarch
foreman-selinux-1.13.0-1.el7.noarch
foreman-libvirt-1.13.0-1.el7.noarch
foreman-release-scl-3-1.el7.noarch
tfm-rubygem-foreman-tasks-0.8.2-1.fm1_13.el7.noarch
foreman-1.13.0-1.el7.noarch
foreman-postgresql-1.13.0-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.1.1-1.fm1_13.el7.noarch
foreman-installer-1.13.0-1.el7.noarch
foreman-release-1.13.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.8.0-1.el7.noarch
foreman-cli-1.13.0-1.el7.noarch
How reproducible:
Always
Steps to Reproduce:
1. Install latest ansible 2.x version
2. Setup ansible plugin as per https://theforeman.org/plugins/foreman_ansible/0.x/index.html#2.Installation
3. Run any ansible playbook and see if the reports are sent to foreman
Actual results:
ansible playbook runs not reported to foreman while using ansible 2.x version
Expected results:
All ansible versions should be supported, currently it looksl ike only ansible-1.9 is supported.
Additional info:
Comment 1sthirugn@redhat.com
2016-10-11 13:16:19 UTC
Edit:
Expected results:
All ansible versions should be supported, currently it looks like only ansible-1.x is supported. ansible-2.x fails.
I was not able to reproduce, it runs fine on my ansible-2.1.2.0-1.fc24.noarch
Comment 4sthirugn@redhat.com
2017-01-05 19:05:50 UTC
(In reply to Ohad Levy from comment #3)
> I was not able to reproduce, it runs fine on my ansible-2.1.2.0-1.fc24.noarch
Thanks, I haven't played with 6.3 build in a while, please move this to ON_QA if you think it works fine now. I or some other QE will get to this eventually.
Comment 5Daniel Lobato Garcia
2017-01-26 15:56:34 UTC
Moved to on_qa, please test with the latest foreman_ansible version.
Comment 6sthirugn@redhat.com
2017-03-08 16:25:18 UTC
Works fine in Satellite 6.3 Snap 8.
# rpm -q ansible
ansible-2.2.1.0-1.el7.noarch
# rpm -q satellite
satellite-6.3.0-11.1.beta.el7sat.noarch
Comment 7Satellite Program
2018-02-21 16:49:54 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:0336