VERIFIED. @Satellite 6.10.4 Snap3 satellite-clone-3.0.0-1.el7sat.noarch by the reproducer described in comment#0 # satellite-clone -y ... TASK [satellite-clone : Check full backup is present] ************************* Tuesday 22 March 2022 07:25:32 -0400 (0:00:00.088) 0:00:32.890 ********* skipping: [sat.example.com] ... >>> the task is now passing However clone process failed almost at its end: TASK [satellite-clone : Test Satellite] *************************************** Tuesday 22 March 2022 08:36:31 -0400 (0:03:13.080) 1:11:31.348 ********* fatal: [sat.example.com]: FAILED! => {"changed": true, "cmd": ["hammer", "ping"], ... pulp3_content: Status: FAIL Server Response: Message: No pulpcore content apps are running at https://sat.example.com/pulp/api/v3. foreman_tasks: Status: FAIL Server Response: Message: some executors are not responding, check /foreman_tasks/dynflow/status >>> this is already handled by BZ 2051912
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 (Satellite Maintenance 6.10.4 Async 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/RHBA-2022:1115