Jammy autoinstall timed out at wait_for_cloudinit

[Qi Zhang]

Jammy live server autoinstall kept failing. From subiquity-server-debug.log, I saw errors as below:

2022-03-19 10:23:55,025 ERROR subiquity.server.server:414 top level error
Traceback (most recent call last):
  File "/snap/subiquity/3119/lib/python3.8/site-packages/subiquity/server/server.py", line 599, in start
    await self.wait_for_cloudinit()
  File "/snap/subiquity/3119/lib/python3.8/site-packages/subiquity/server/server.py", line 510, in wait_for_cloudinit
    status_cp = await asyncio.wait_for(status_coro, 600)
  File "/snap/subiquity/3119/usr/lib/python3.8/asyncio/tasks.py", line 501, in wait_for
    raise exceptions.TimeoutError()
asyncio.exceptions.TimeoutError
2022-03-19 10:23:55,031 DEBUG subiquitycore.common.errorreport:384 generating crash report
2022-03-19 10:23:55,033 INFO subiquitycore.common.errorreport:406 saving crash report 'unknown error crashed with TimeoutError' to /var/crash/1647685435.031627178.unknown.crash

For a full log, please refer to attachment.

But I didn't see any error in cloud-init result:
root@ubuntu-server:/home/installer# cat /var/lib/cloud/data/result.json
{
 "v1": {
  "datasource": "DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud,/dev/sr1][dsmode=net]",
  "errors": []
 }
}

Can anyone help me out of this?

[Qi Zhang (keiraqiz)]

Related logs are attached. Please let me know if any other information is needed. Thanks!

[Qi Zhang (keiraqiz)]

From syslog:

Mar 19 10:11:48 ubuntu-server systemd[1]: Starting casper-md5check Verify Live ISO checksums...
...
Mar 19 10:24:32 ubuntu-server systemd[1]: Finished casper-md5check Verify Live ISO checksums.

And the timeout error was reported at:
2022-03-19 10:13:55,943 DEBUG curtin.reporting.start.subiquity/Meta/status_GET:45 start: subiquity/Meta/status_GET:
2022-03-19 10:23:55,025 ERROR subiquity.server.server:414 top level error

May I consider this timeout error was because of casper-md5check?