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.
Description of problem:
A group of hosts was selected, and an ansible roles run was initiated from Satellite. 1 of the hosts has an issue which displays a DEPRECATION WARNING for one of the tasks. This warning appears in every job tasks for all of the hosts, not just for the host that has the issue. When the ansible roles are ran against individual hosts (1 at a time), the DEPRECATION WARNING does not display for any of the hosts (except for the one having issues).
An example where the error is on host2, however, the playbook is ran against host1:
~~~
TASK [Gathering Facts]**********************************************************
ok: [host1]
[DEPRECATION WARNING]: Distribution redhat 8.3 on host host2 should use /usr/libexec/platform-python, but is using
/usr/bin/python for backward compatibility with prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for more information. This feature will
be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
~~~
Version-Release number of selected component (if applicable):
Satellite 6.8
How reproducible:
always
Steps to Reproduce:
1. Select a number of hosts to run ansible roles on (make sure one of the hosts will throw the DEPRECATION WARNING message)
2. Review the tasks for any of the individual hosts, and you will see the same unrelated host appearing in the DEPRECATION WARNING
3.
Actual results:
DEPRECATION WARNING message for 1 particular host appears in the job tasks for all hosts that ran in the same group
Expected results:
expect the DEPRECATION WARNING message to only be displayed for the task of the host the warning is for
Additional info:
It has the same symptoms and the same root cause as #1912941, marking as dup, because it will be solved within the same upstream ticket.
*** This bug has been marked as a duplicate of bug 1912941 ***