From a627460579ce51196c8407d3ba98300c53e806af Mon Sep 17 00:00:00 2001 From: Evgeni Golov Date: Tue, 4 Jun 2024 09:36:13 +0200 Subject: [PATCH] don't stop/start crond and don't start services after restore foreman-maintain takes care of all that, no need to duplicate work --- roles/satellite-clone/tasks/main.yml | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/roles/satellite-clone/tasks/main.yml b/roles/satellite-clone/tasks/main.yml index 8ffe2f6..c1dcfa0 100644 --- a/roles/satellite-clone/tasks/main.yml +++ b/roles/satellite-clone/tasks/main.yml @@ -257,23 +257,9 @@ - name: Finalize clone block: - # Cron services can interfere with restoring the backup - - name: stop crond - systemd: - name: crond - state: stopped - - name: restore using foreman-maintain command: foreman-maintain restore --assumeyes {{ backup_dir }} - - name: start crond - systemd: - name: crond - state: started - - - name: Restart services - command: foreman-maintain service start - # We don't use pause module here because it displays a prompt # to use ctrl+c which would break out of a production script. - name: Wait for foreman-tasks service to start