Verified on 6.12.1 snap 1

satellite-clone is running successfully with ansible-core 2.13.

Steps to Reproduce:
1) Set up prerequisites for running satellite-clone on a RHEL8.6 machine
2) Install satellite-clone
3) Check versions:
      # rpm -qa satellite-clone ansible-core
      satellite-clone-3.2.0-2.el8sat.noarch
      ansible-core-2.13.3-1.el8.x86_64
4) # satellite-clone -y

Results:
satellite-clone ran successfully.


Note:
I got a failure at 

TASK [satellite-clone : Test Satellite] ******************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["hammer", "ping"], "delta": "0:00:58.997593", "end": "2022-12-15 12:33:59.310704", "msg": "non-zero return code", "rc": 1, "start": "2022-12-15 12:33:00.313111", "stderr": "", "stderr_lines": [], "stdout": "database:         \n    Status:          ok\n    Server Response: Duration: 1ms\ncandlepin:        \n    Status:          ok\n    Server Response: Duration: 20977ms\ncandlepin_auth:   \n    Status:          ok\n    Server Response: Duration: 2302ms\ncandlepin_events: \n    Status:          ok\n    message:         0 Processed, 0 Failed\n    Server Response: Duration: 1ms\nkatello_events:   \n    Status:          ok\n    message:         0 Processed, 0 Failed\n    Server Response: Duration: 21ms\npulp3:            \n    Status:          ok\n    Server Response: Duration: 2581ms\npulp3_content:    \n    Status:          ok\n    Server Response: Duration: 918ms\nforeman_tasks:    \n    Status:          FAIL\n    Server Response: Message: The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer", "stdout_lines": ["database:         ", "    Status:          ok", "    Server Response: Duration: 1ms", "candlepin:        ", "    Status:          ok", "    Server Response: Duration: 20977ms", "candlepin_auth:   ", "    Status:          ok", "    Server Response: Duration: 2302ms", "candlepin_events: ", "    Status:          ok", "    message:         0 Processed, 0 Failed", "    Server Response: Duration: 1ms", "katello_events:   ", "    Status:          ok", "    message:         0 Processed, 0 Failed", "    Server Response: Duration: 21ms", "pulp3:            ", "    Status:          ok", "    Server Response: Duration: 2581ms", "pulp3_content:    ", "    Status:          ok", "    Server Response: Duration: 918ms", "foreman_tasks:    ", "    Status:          FAIL", "    Server Response: Message: The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer"]}

I imagine that this is unrelated to this specific BZ. Does this needs it's own separate BZ or is this a failure in my setup?

@gsulliva 

This is know issue, foreman-tasks are taking long to start. (pls no private verification comments)

satellite-clone should use adaptive waiting for services to start, similar what foreman-maintain has

So, pls file a new BZ in this spirit. Thanks

comment#10 is response to the question raised in comment#2

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 (Critical: Satellite 6.12.1 Async Security 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-2023:0261

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days