Ubuntu 22.04 (v20240301) boot delay of ~2 minutes due to timeout in DataSourceMAAS

[Jacopo Rota]

On every MAAS version when I deploy ubuntu 22.04 (https://images.maas.io/ephemeral-v3/stable/jammy/amd64/20240301/) the os is properly installed, but when the machine reboots there is a delay in the startup and looking at the journalctl logs it's possible to see a timeout of ~2 minutes for the DataSourceMAAS that failed to make some requests to the rack.

```
Mar 13 09:25:05 ubuntu cloud-init[572]: Cloud-init v. 23.4.3-0ubuntu0~20.04.1 running 'init-local' at Wed, 13 Mar 2024 09:25:05 +0000. Up 4.05 seconds.
Mar 13 09:25:05 ubuntu cloud-init[572]: 2024-03-13 09:25:05,794 - handlers.py[WARNING]: Failed posting event: {"name": "init-local/check-cache", "description": "attempting to read from cache [trust]", "event_type": "start", "origin": "cloudinit", "timestamp": 1710321905.77>
Mar 13 09:25:05 ubuntu cloud-init[572]: 2024-03-13 09:25:05,795 - handlers.py[WARNING]: Failed posting event: {"name": "init-local/check-cache", "description": "no cache found", "event_type": "finish", "origin": "cloudinit", "timestamp": 1710321905.7760243, "result": "SUCC>
Mar 13 09:25:05 ubuntu cloud-init[572]: 2024-03-13 09:25:05,796 - handlers.py[WARNING]: Failed posting event: {"name": "init-local/search-MAAS", "description": "searching for local data from DataSourceMAAS", "event_type": "start", "origin": "cloudinit", "timestamp": 171032>
Mar 13 09:25:34 ubuntu systemd[1]: systemd-fsckd.service: Succeeded.
Mar 13 09:27:12 ubuntu cloud-init[572]: 2024-03-13 09:27:12,029 - url_helper.py[ERROR]: Timed out, no response from urls: ['http://10.0.2.250:5248/MAAS/metadata/2012-03-01/meta-data/instance-id']
Mar 13 09:27:12 ubuntu cloud-init[572]: 2024-03-13 09:27:12,030 - DataSourceMAAS.py[CRITICAL]: Giving up on md from ['http://10.0.2.250:5248/MAAS/metadata/2012-03-01/meta-data/instance-id'] after 126 seconds
Mar 13 09:27:12 ubuntu cloud-init[572]: 2024-03-13 09:27:12,036 - handlers.py[WARNING]: Failed posting event: {"name": "init-local/search-MAAS", "description": "no local data found from DataSourceMAAS", "event_type": "finish", "origin": "cloudinit", "timestamp": 1710322032>
Mar 13 09:27:12 ubuntu systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped.
Mar 13 09:27:12 ubuntu cloud-init[572]: 2024-03-13 09:27:12,169 - handlers.py[WARNING]: Failed posting event: {"name": "init-local", "description": "searching for local datasources", "event_type": "finish", "origin": "cloudinit", "timestamp": 1710322032.1686447, "result": >
Mar 13 09:27:12 ubuntu cloud-init[572]: 2024-03-13 09:27:12,169 - handlers.py[WARNING]: Multiple consecutive failures in WebHookHandler. Cancelling all queued events.
```

The issue here is the delay of ~2 minutes in the boot process

[Chad Smith (chad.smith)]

If possible, can we run cloud-init collect-logs on the affected system which will grab us journalctl output and all necessary logs from /var/log/cloud-init*log and /run/cloud-init/ which will help debug what network configuration cloud-init attempted to write out on this system and why.

[Alec (paravz)]

Can't clearly find where this was fixed. Is it a specific clouid-init version and/or maas version/commit? Looking for a fix for older maas and default ubuntu 22.04 maas image.

[James Falcon (falcojr)]

Alec, this bug is believed to be fixed via https://github.com/canonical/cloud-init/pull/5068 and available in cloud-init 24.2.