This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2134166 - Deprecation of callback_whitelist in favor of callbacks_enabled
Summary: Deprecation of callback_whitelist in favor of callbacks_enabled
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-12 16:30 UTC by Ondrej Gajdusek
Modified: 2024-06-06 12:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:35:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-14709 0 None Migrated None 2024-06-06 12:35:23 UTC

Description Ondrej Gajdusek 2022-10-12 16:30:03 UTC 
Description of problem:
A deprecation warning pops up when Ansible roles are run on the host.


[DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names 
to new standard, use callbacks_enabled instead. This feature will be removed 
from ansible-core in version 2.15. Deprecation warnings can be disabled by 
setting deprecation_warnings=False in ansible.cfg.

Version-Release number of selected component (if applicable):
Satellite 6.12.0 snap 14

How reproducible:
always

Steps to Reproduce:
1. Have Satellite installed on RHEL 8.7 system with ansible-core-2.13.3-1.el8.x86_64 installed
2. Have a host registered to Satellite
3. Run Ansible roles on this host

Actual results:
A deprecation warning is shown.

Expected results:
No deprecation warning should be shown.

Additional info:
Found during verification of BZ2125585.
Comment 1 Evgeni Golov 2022-10-13 08:37:22 UTC 
The version of the config as we deploy today will actually *break* with ansible-core 2.15 once they remove the `callback_whitelist` option.

@aruzicka is currently working on changing how we configure ansible, and part of that change will also include adding the "enabled" notation of the config (see https://github.com/theforeman/puppet-foreman_proxy/pull/777).

We'll *remove* the "whitelist" notation once we do not support deploying on platforms that have older Ansible versions (which we still do upstream).
Comment 12 Brad Buckingham 2023-11-02 17:44:31 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 14 Brad Buckingham 2023-12-01 18:02:22 UTC 
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.
Comment 15 Eric Helms 2024-06-06 12:35:24 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.