However, the current one bionic-server-cloudimg-arm64.img (10-Jun-2020, f73471e3ea879e4fd77f4811673581f5) differs from what I have downloaded earlier bionic-server-cloudimg-arm64.img (May 24 00:59 UTC+8, 30d459e0dc0562e629d3683970e55efa).
I tried both today, and the current image (10-Jun-2020) won't reproduce this issue when launching ~10 bionic instances. The previous image (May 24 2020) is still able to reproduce this issue.
I am keeping testing by launching more instances to see if this issue is invalid now.
Thank @admcleod for re-testing with the current bionic image.
The image being used to launch the instances is downloaded from http:// cloud-images. ubuntu. com/bionic/ current/ bionic- server- cloudimg- arm64.img
However, the current one bionic- server- cloudimg- arm64.img (10-Jun-2020, f73471e3ea879e4 fd77f4811673581 f5) differs from what I have downloaded earlier bionic- server- cloudimg- arm64.img (May 24 00:59 UTC+8, 30d459e0dc0562e 629d3683970e55e fa).
I tried both today, and the current image (10-Jun-2020) won't reproduce this issue when launching ~10 bionic instances. The previous image (May 24 2020) is still able to reproduce this issue.
I am keeping testing by launching more instances to see if this issue is invalid now.