Bug 1884033

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/22804 has been resolved.

FailedQA.

@Satellite 6.8.1 Snap1
tfm-rubygem-foreman_ansible-5.1.3.1-1.el7sat.noarch

when tried to use reproducer described in comment#0:




PLAY RECAP *********************************************************************
dhcp-2-126.example.com : ok=5    changed=1    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0
500 Server Error: Internal Server Error
Exit status: 0

>>> any Ansible REX job, though successful, takes a bit more time now as there is 500 ISE at the end

If the change requires now an updated foreman callback why don't we deliver it also via rpm

Tried to update callback, however 500 ISE persisted

cd /usr/lib/python2.7/site-packages/ansible/plugins/callback/
mv foreman.py foreman.py.orig
wget https://raw.githubusercontent.com/theforeman/foreman-ansible-modules/develop/plugins/callback/foreman.py

While this should not affect the 500 error, just downloading the callback from github and placing it into the ansible folder won't work (and is not what customers are supposed to do).

See also https://bugzilla.redhat.com/show_bug.cgi?id=1800870#c18

(In reply to Lukas Pramuk from comment #3)

> If the change requires now an updated foreman callback why don't we deliver
> it also via rpm

we do, it's in ansible-collection-redhat-satellite -- but that code is not used by default.

VERIFIED.

@Satellite 6.8.1 Snap3
foreman-2.1.2.21-1.el7sat.noarch
tfm-rubygem-foreman_ansible-5.1.3.1-1.el7sat.noarch
ansible-collection-redhat-satellite-1.3.0-1.el7sat.noarch
ansible-2.9.15-1.el7ae.noarch

by the manual reproducer based on description in comment#0 and comment#6:

1) Update foreman callback by installing ansible-collection-redhat-satellite and changing callback name from "foreman" to "redhat.satellite.foreman"

# satellite-maintain packages install ansible-collection-redhat-satellite
# sed -i 's/^callback_whitelist\s*=.*/callback_whitelist = redhat.satellite.foreman/' /etc/foreman-proxy/ansible.cfg

(expect this setting being overrun by an installer run)

>>> foreman callback is shipped by ansible so Satellite has no control over when it is updated
 
2) Change the Settings > General > Out of sync interval = 5 min , Ansible > Ansible report timeout = 10 mins
3) Assign an Ansible Role to a Host
4) Apply the Role(s) via REX to the Host

5) Refresh the Host details repeatedly to watch "Configuration" status turning from "Active" to "Out of sync"

>>> "Out of sync" status worn after "Out of sync interval" + "Ansible report timeout" time = 15 mins

6) Yet check the origin of the generated report by clicking [Reports] button at the host details page

>>> origin is set to "ansible" (A) icon, instead of "N/A"

>>> was hesitant to verify this BZ as the fix requires callback update which at the moment are manual steps since the foreman callback is currently shipped by ansible and not Satellite but I expect in near future "foreman" callback being replaced by "redhat.satellite.foreman" callback

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 (Satellite 6.8.1 Async Bug Fix Update), 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/RHBA-2020:5180