VERIFIED.

@Satellite Stream Snap49
ansible-collection-redhat-satellite-4.0.0-2.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_stream_Composes_Satellite_stream_RHEL8                Satellite Stream RHEL8
Satellite_Engineering_Satellite_stream_Composes_Satellite_Maintenance_stream_RHEL8    Satellite Maintenance Stream RHEL8

# satellite-maintain upgrade run --target-version 6.16.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/03/01 11:38:07 | Ansible | 1       | 0         | 0      | 0                | 8       | 0      
---|------------------------------------------------|---------------------|---------|---------|-----------|--------|------------------|---------|--------

>>> REX action and namely 'redhat.satellite.foreman' callback finished successfully

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.