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 2264918 - Support Satellite Ansible Collection running on Python 3.12
Summary: Support Satellite Ansible Collection running on Python 3.12
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.13.7
Assignee: Odilon Sousa
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-19 16:29 UTC by Odilon Sousa
Modified: 2024-02-29 20:35 UTC (History)
3 users (show)

Fixed In Version: ansible-collection-redhat-satellite-3.9.0-3.el8sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2264353
Environment:
Last Closed: 2024-02-29 20:35:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-23302 0 None None None 2024-02-19 16:29:53 UTC
Red Hat Issue Tracker SAT-23393 0 None None None 2024-02-19 16:35:03 UTC
Red Hat Product Errata RHSA-2024:1061 0 None None None 2024-02-29 20:35:19 UTC

Description Odilon Sousa 2024-02-19 16:29:39 UTC 
+++ This bug was initially created as a clone of Bug #2264353 +++

Description of problem:
Ansible will start using Python 3.12 in EL8 when it's updated to 2.16.3-2[1]

We need to ensure our collection pulls in the right dependencies for that Python version, as otherwise things might break.

[1] https://kojihub.stream.centos.org/koji/buildinfo?buildID=50584

Version-Release number of selected component (if applicable):
Any supported Satellite versions on EL8

How reproducible:
100%

Steps to Reproduce:
1. install ansible-core 2.16.3-2 (or newer)
2. run an Ansible role via Satellite

Actual results:
Execution works, but there is no report in Satellite

Expected results:
report works as it did before

Additional info:
Previously: BZ#2170034
Upstream: https://github.com/theforeman/foreman-packaging/pull/10428
Comment 1 Lukas Pramuk 2024-02-27 16:49:14 UTC 
VERIFIED.

@Satellite 6.13.7 Snap2
ansible-collection-redhat-satellite-3.9.0-3.el8sat.noarch

A) by this simple reproducer:

# rpm -qR ansible-collection-redhat-satellite | grep core
(ansible >= 2.9 or ansible-core)
(python3.11-pyyaml if (ansible-core >= 2.14.2-3 and ansible-core < 2.16.3-2))
(python3.11-requests if (ansible-core >= 2.14.2-3 and ansible-core < 2.16.3-2))
(python3.12-pyyaml if ansible-core >= 2.16.3-2)
(python3.12-requests if ansible-core >= 2.16.3-2)
(python38-pyyaml if ansible-core < 2.13)
(python38-requests if ansible-core < 2.13)
(python39-pyyaml if (ansible-core >= 2.13 and ansible-core < 2.14.2-3))
(python39-requests if (ansible-core >= 2.13 and ansible-core < 2.14.2-3))

# rpm -qR rubygem-smart_proxy_ansible | grep runner
ansible-runner >= 2

>>> requirements are RHEL8.10 ready


B) by running Satellite in-place upgrade of RHEL to RHEL-8.10 (using internal RHEL candidate repo)

# dnf repolist
...
repo id                                                                           repo name
AppStream                                                                         AppStream
BaseOS                                                                            BaseOS
Satellite_Engineering_Satellite_6_13_Composes_Satellite_6_13_RHEL8                Satellite 6.13 RHEL8
Satellite_Engineering_Satellite_6_13_Composes_Satellite_Maintenance_6_13_RHEL8    Satellite Maintenance 6.13 RHEL8

# satellite-maintain upgrade run --target-version 6.13.z -w repositories-setup,repositories-validate -y 
...
Update package(s) :                                                   [OK]
--------------------------------------------------------------------------------
Procedures::Installer::Upgrade:                                       [OK]
--------------------------------------------------------------------------------
Execute upgrade:run rake task:                                        [OK]
--------------------------------------------------------------------------------
...
--------------------------------------------------------------------------------
Upgrade finished.

>>> there are now no dependency issues on RHEL-8.10 as in-place upgrade to RHEL-8.10 is successful

C) by running Ansible REX at Satellite on RHEL-8.10

# jobid=$(hammer --csv host ansible-roles play --name $(hostname) | awk -F, 'NR>1{print$2}')

# hammer job-invocation output --id $jobid --host $(hostname)
[DEPRECATION WARNING]: ANSIBLE_COLLECTIONS_PATHS option, does not fit var 
naming standard, use the singular form ANSIBLE_COLLECTIONS_PATH instead. This 
feature will be removed from ansible-core in version 2.19. Deprecation warnings
 can be disabled by setting deprecation_warnings=False in ansible.cfg.
...

PLAY RECAP *********************************************************************
satellite.example.com : ok=6    changed=1    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
Exit status: 0

# hammer config-report list --search host=$(hostname),applied=1
---|------------------------------------------------|---------------------|---------|---------|-----------|--------|------------------|---------|--------
ID | HOST                                           | LAST REPORT         | ORIGIN  | APPLIED | RESTARTED | FAILED | RESTART FAILURES | SKIPPED | PENDING
---|------------------------------------------------|---------------------|---------|---------|-----------|--------|------------------|---------|--------
1  | satellite.example.com                          | 2024/02/27 11:51:20 | Ansible | 1       | 0         | 0      | 0                | 8       | 0      
---|------------------------------------------------|---------------------|---------|---------|-----------|--------|------------------|---------|--------

>>> REX action and namely 'redhat.satellite.foreman' callback finished successfully
Comment 7 errata-xmlrpc 2024-02-29 20:35:18 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: Red Hat Satellite 6 security and 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/RHSA-2024:1061
Note You need to log in before you can comment on or make changes to this bug.