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-19 18:32:19 UTC
Description of problem:
ansible-playbook runs not reported to Satellite, running ansible 1.9
Version-Release number of selected component (if applicable):
# rpm -qa | grep satellite
satellite-installer-6.3.0-1.el7sat.noarch
satellite-cli-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-1.0.0-1.git.2.94b76fc.el7.noarch
satellite-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch
# rpm -qa | grep ansible
ansible1.9-1.9.6-2.el7.noarch
tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch
How reproducible:
Always
Steps to Reproduce:
1. ansible callback is setup properly in satellite and `ansible -m setup localhost` ran without any errors
2. Create a simple ansible module. My main.yml just had:
---
- hosts: all
remote_user: root
tasks:
- name: enable selinux
command: /sbin/setenforce 1
3. # cat /etc/ansible/hosts
...
...
rhsm-qe-3.rhq.lab.eng.bos.redhat.com
192.168.100.5
4. Run playbook:
# ansible-playbook /etc/ansible/roles/ntp/tasks/main.yml
PLAY [all] ********************************************************************
GATHERING FACTS ***************************************************************
ok: [192.168.100.5]
ok: [rhsm-qe-3.rhq.lab.eng.bos.redhat.com]
TASK: [enable selinux] ********************************************************
changed: [192.168.100.5]
changed: [rhsm-qe-3.rhq.lab.eng.bos.redhat.com]
PLAY RECAP ********************************************************************
192.168.100.5 : ok=2 changed=1 unreachable=0 failed=0
rhsm-qe-3.rhq.lab.eng.bos.redhat.com : ok=2 changed=1 unreachable=0 failed=0
Actual results:
No reports created in Satellite after the successful playbook run as shown above.
Expected results:
Reports created in Satellite after the successful playbook run as shown above.
Additional info:
Earlier I reported this for Ansible 2.x versions (https://bugzilla.redhat.com/show_bug.cgi?id=1383697) but in Satellite 6.3 snap 5 - it failed for Ansible 1.9 as well.
Comment 2sthirugn@redhat.com
2016-10-19 20:15:26 UTC
Configuration error. It works fine after fixing the configuration.
Description of problem: ansible-playbook runs not reported to Satellite, running ansible 1.9 Version-Release number of selected component (if applicable): # rpm -qa | grep satellite satellite-installer-6.3.0-1.el7sat.noarch satellite-cli-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch tfm-rubygem-foreman_theme_satellite-1.0.0-1.git.2.94b76fc.el7.noarch satellite-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch # rpm -qa | grep ansible ansible1.9-1.9.6-2.el7.noarch tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch How reproducible: Always Steps to Reproduce: 1. ansible callback is setup properly in satellite and `ansible -m setup localhost` ran without any errors 2. Create a simple ansible module. My main.yml just had: --- - hosts: all remote_user: root tasks: - name: enable selinux command: /sbin/setenforce 1 3. # cat /etc/ansible/hosts ... ... rhsm-qe-3.rhq.lab.eng.bos.redhat.com 192.168.100.5 4. Run playbook: # ansible-playbook /etc/ansible/roles/ntp/tasks/main.yml PLAY [all] ******************************************************************** GATHERING FACTS *************************************************************** ok: [192.168.100.5] ok: [rhsm-qe-3.rhq.lab.eng.bos.redhat.com] TASK: [enable selinux] ******************************************************** changed: [192.168.100.5] changed: [rhsm-qe-3.rhq.lab.eng.bos.redhat.com] PLAY RECAP ******************************************************************** 192.168.100.5 : ok=2 changed=1 unreachable=0 failed=0 rhsm-qe-3.rhq.lab.eng.bos.redhat.com : ok=2 changed=1 unreachable=0 failed=0 Actual results: No reports created in Satellite after the successful playbook run as shown above. Expected results: Reports created in Satellite after the successful playbook run as shown above. Additional info: Earlier I reported this for Ansible 2.x versions (https://bugzilla.redhat.com/show_bug.cgi?id=1383697) but in Satellite 6.3 snap 5 - it failed for Ansible 1.9 as well.