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.

Bug 1934110

Summary:	Foreman callback is always used
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Ansible - Configuration Management	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Danny Synk <dsynk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	oezr
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ansible-collection-redhat-satellite-2.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:10:12 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:

Description Adam Ruzicka 2021-03-02 14:24:20 UTC

Description of problem:
When satellite used ansible-playbook, it disabled the callback plugin for all runs, except when roles were being applied. 

Version-Release number of selected component (if applicable):
tfm-rubygem-foreman_ansible-6.1.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Bump ansible verbosity to -vvvv in Administer > Settings > Ansible > Default verbosity level
2. Run for example ls -la / using ansible
3. Check the output

Actual results:
Line "Loading callback plugin foreman of type notification, v2.0 from /usr/lib/python2.7/site-packages/ansible/plugins/callback/foreman.py" appears in the output, run is slow.


Expected results:
The callback plugin is not loaded, no such line in output, faster run.


Additional info:
The current callback plugin is not exactly ideal performance wise and might cause severe performance degradation, depending on number of hosts and the playbook being run.

Comment 1 Ondřej Ezr 2021-03-05 12:30:19 UTC

Created redmine issue https://projects.theforeman.org/issues/32020 from this bug

Comment 2 Bryan Kearney 2021-03-05 16:03:26 UTC

Upstream bug assigned to aruzicka

Comment 3 Bryan Kearney 2021-03-05 16:03:29 UTC

Upstream bug assigned to aruzicka

Comment 5 Danny Synk 2021-06-22 17:29:54 UTC

Steps to Test:

1. Register a content host to Satellite and configure it for remote execution using the Global Registration Template.
2. In the Satellite webUI, increase the Ansible verbosity to Level 4 using the Administer > Settings > Ansible > Default verbosity level setting.
3. In the Satellit webUI, navigate to Hosts > All Hosts > [hostname] and click the "Schedule remote job" button.
4. On the job invocation page, set the job category to "Ansible Commands" and enter "ls -la" in the "command" field.
5. Click the "Submit" button.

Expected Results:

The foreman notification callback is not loaded, and the job completes faster than a Satellite that does use this callback.

Actual Results:

The foreman notification callback is not loaded, and the job completes faster than a Satellite that does use this callback.

On Satellite 6.10.0, snap 5, the job completes in 11 seconds, and the output contains the following line:

    output: "[WARNING]: Skipping callback plugin 'theforeman.foreman.foreman', unable
      to\r\nload\n"

On Satellite 6.9.3, snap 3, the same job completes in 31 seconds, and the output contains the following line:

    output: 'Loading callback plugin foreman of type notification, v2.0 from /usr/lib/python2.7/site-packages/ansible/plugins/callback/foreman.pyc

Verified on Satellite 6.10, snap 5 (tfm-rubygem-foreman_ansible-6.3.0-1.el7sat.noarch).

Comment 8 errata-xmlrpc 2021-11-16 14:10:12 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 (Moderate: Satellite 6.10 Release), 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-2021:4702