Comment 2 for bug 1897952

After some discussions, I decided to launch another 12 instances to see if the issues had been resolved. Out of 12 instances, 4 failed to communicate during the snapd.seeded.service with the error:

Sep 30 20:47:31 ip-10-0-1-134 systemd[1]: Starting Wait until snapd is fully seeded...
Sep 30 20:48:22 ip-10-0-1-134 snap[1028]: error: cannot communicate with server: timeout exceeded while waiting for response
Sep 30 20:48:22 ip-10-0-1-134 systemd[1]: snapd.seeded.service: Main process exited, code=exited, status=1/FAILURE
Sep 30 20:48:22 ip-10-0-1-134 systemd[1]: snapd.seeded.service: Failed with result 'exit-code'.
Sep 30 20:48:22 ip-10-0-1-134 systemd[1]: Failed to start Wait until snapd is fully seeded.

I have kept one of these systems up and added the SSH keys of the snapd team:

ssh ubuntu@34.215.224.87

ssh-import-id lp:pedronis lp:mvo lp:zyga lp:mvo lp:sergio-j-cazzolato lp:morrisong lp:maciek-borzecki lp:anonymouse67