einfachIT / ansible-collection-epic

2 stars 0 forks source link

Decommissioning of respberries fails #31

Open Bassinator opened 1 month ago

Bassinator commented 1 month ago

running the decomission_respberries playbooks fails like this:

PLAY [decommission raspberries] **************************************************************************************************************************************************************************************

TASK [reset machine to plain os by restoring image from a recovery partition] ****************************************************************************************************************************************
ASYNC POLL on epic-docker-host: jid=j608773115272.21622 started=1 finished=0
ASYNC POLL on epic-docker-host: jid=j608773115272.21622 started=1 finished=0
[WARNING]: sftp transfer mechanism failed on [mighty-mouse.fritz.box]. Use ANSIBLE_DEBUG=1 to see detailed information
[WARNING]: scp transfer mechanism failed on [mighty-mouse.fritz.box]. Use ANSIBLE_DEBUG=1 to see detailed information
fatal: [epic-docker-host]: FAILED! => {"msg": "Failed to connect to the host via ssh: ssh: connect to host mighty-mouse.fritz.box port 22: Connection refused"}

PLAY RECAP ***********************************************************************************************************************************************************************************************************
epic-docker-host           : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

Reason might be the async call of the restore command, which makes sense to identify issues with this command, which is not possible via fire and forget. That's why I implemented this.

To fix this the reboot issued by the restore command on the epicPiOS image needs to be scheduled but not immediately issued. I implemented it locally but forgot to incorporate it in the epicPiOS image. This issue needs to be fixed on the epicPiOS repository