Sync task error: restore ES snapshot - "index_not_found_exception"

[pjotrek-b]

Starting the syncronization script (manually on atom-edit-server), I get an error that there is no inde to handle:

TASK [artefactual.ansible-atom-replication : Restore ES snapshot - Single Index] **********************************************************************************************************************************
Thursday 18 September 2025 10:24:33 +0000 (0:00:00.141) 0:01:17.907 ****
skipping: [atom-edit-server]
[ERROR]: Task failed: Module failed: Status code was 404 and not [200]: HTTP Error 404: Not Found
Origin: /usr/share/nginx/atom-replication/roles/artefactual.ansible-atom-replication/tasks/es-restore-backup.yml:51:3

49
50
51 - name: "Restore ES snapshot - Single Index"
^ column 3

fatal: [atom-ro-server]: FAILED! => {"changed": false, "content_length": "231", "content_type": "application/json; charset=UTF-8", "elapsed": 0, "json": {"error": {"index": "atom", "index_uuid": "na", "reason"
: "no such index", "root_cause": [{"index": "atom", "index_uuid": "na", "reason": "no such index", "type": "index_not_found_exception"}], "type": "index_not_found_exception"}, "status": 404}, "msg": "Status co
de was 404 and not [200]: HTTP Error 404: Not Found", "redirected": false, "status": 404, "url": "http://127.0.0.1:9200/_snapshot/backup-repo/backup-repo/_restore?wait_for_completion=true"}

This may make sense, as it's a fresh-vanilla install, and the index /may/ in fact be not present / generated yet.

[pjotrek-b]

More like that:

TASK [artefactual.ansible-atom-replication : Close index to avoid problems while restoring the backup on ES read-only server - Single Index] **********************************************************************
Thursday 18 September 2025 14:17:55 +0000 (0:00:00.964) 0:01:16.801 ****
skipping: [atom-edit-server]
[ERROR]: Task failed: Module failed: Status code was 404 and not [200]: HTTP Error 404: Not Found
Origin: /usr/share/nginx/atom-replication/roles/artefactual.ansible-atom-replication/tasks/es-restore-backup.yml:31:3

29 remote_src: true
30
31 - name: "Close index to avoid problems while restoring the backup on ES read-only server - Single Index"
^ column 3

fatal: [atom-ro-server]: FAILED! => {"changed": false, "content_length": "339", "content_type": "application/json; charset=UTF-8", "elapsed": 0, "json": {"error": {"index": "atom", "index_uuid": "na", "reason": "no such index", "resource.id": "atom", "resource.type": "index_or_alias", "root_cause": [{"index": "atom", "index_uuid": "na", "reason": "no such index", "resource.id": "atom", "resource.type": "index_or_alias", "type": "index_not_found_exception"}], "type": "index_not_found_exception"}, "status": 404}, "msg": "Status code was 404 and not [200]: HTTP Error 404: Not Found", "redirected": false, "status": 404, "url": "http://127.0.0.1:9200/atom/_close"}
...ignoring