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 2142514 - Satellite-clone not working if ansible-core 2.13 is installed
Summary: Satellite-clone not working if ansible-core 2.13 is installed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.13.0
Assignee: Evgeni Golov
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-14 09:58 UTC by Ladislav Vasina
Modified: 2023-05-19 09:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2150108 2170874 (view as bug list)
Environment:
Last Closed: 2023-05-03 13:22:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-13950 0 None None None 2022-11-18 00:26:09 UTC
Red Hat Knowledge Base (Solution) 6990044 0 None None None 2022-12-15 21:32:54 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:22:56 UTC

Description Ladislav Vasina 2022-11-14 09:58:51 UTC
Description of problem:
I have found out that satellite-clone is failing if ansible-core 2.13 is installed on target RHEL.
This is happening because ansible-core 2.13 needs python 3.9 but satellite-clone is being run with python 3.8 which doesn't have the ansible python package installed.

Version-Release number of selected component (if applicable):
RHEL 8.6
ansible-core-2.13.3-1.el8.x86_64
satellite-clone-3.2.0-1.el8sat.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Install and try running satellite-clone


Actual results:
# satellite-clone -y
Traceback (most recent call last):
  File "/usr/sbin/satellite-clone", line 98, in <module>
    main()
  File "/usr/sbin/satellite-clone", line 82, in main
    from ansible.cli.playbook import PlaybookCLI


ModuleNotFoundError: No module named 'ansible'

Expected results:
Satellite clone shouldn't fail.

Additional info:
See Comment1

Comment 3 Evgeni Golov 2022-12-01 07:49:16 UTC
To workaround the issue, you need to replace the Python version satellite-clone is being executed with:

sed -i 's/python3.8/python3.9/' /usr/sbin/satellite-clone

Comment 4 Griffin Sullivan 2023-01-23 17:05:48 UTC
Verified on Satellite 6.13 snap 7

Satellite clone is running successfully with ansible-core 2.13

Steps to reproduce:

1) Get a satellite and a base rhel

2) Run the clone to target rhel VM

Results:

satellite-clone -y runs successfully without any issues.

Comment 7 errata-xmlrpc 2023-05-03 13:22:42 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 (Important: Satellite 6.13 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-2023:2097


Note You need to log in before you can comment on or make changes to this bug.