The same problem happens to me, but only when I try to get the plucky
container. I'm running Ubuntu 24.04 with autopkgtest version 5.34ubuntu2
```
sh -x /usr/bin/autopkgtest-build-lxd ubuntu-daily:plucky/amd64
+ set -eu
+ short_opts=hr:
+ long_opts=help,vm,lxd,incus,remote:
+ getopt --name autopkgtest-build-lxd --options hr: --long
help,vm,lxd,incus,remote: -- ubuntu-daily:plucky/amd64
+ eval set -- -- 'ubuntu-daily:plucky/amd64'
+ set -- -- ubuntu-daily:plucky/amd64
+ unset short_opts long_opt
+ COMMAND=
+ true
+ shift
+ break
+ [ -z ]
+ COMMAND=lxc
+ [ -z ubuntu-daily:plucky/amd64 ]
+ IMAGE=ubuntu-daily:plucky/amd64
+ CONTAINER=
+ trap [ -z "$CONTAINER" ] || "$COMMAND" delete -f
"${REMOTE:+$REMOTE:}$CONTAINER" EXIT INT QUIT PIPE
+ proxy_detect
+ AUTOPKGTEST_APT_PROXY=
+ [ -z ]
+ apt-config shell proxy Acquire::http::Proxy
+ RES=
+ eval
+ echo
+ egrep -q (localhost|127\.0\.0\.[0-9]*)
+ [ -n ]
+ generate_container_name
+ true
+ mktemp autopkgtest-prepare-XXX -u
+ CONTAINER=autopkgtest-prepare-Due
+ lxc info autopkgtest-prepare-Due
+ break
+ [ -n ]
+ lxc launch ubuntu-daily:plucky/amd64 autopkgtest-prepare-Due
Launching autopkgtest-prepare-Due
+ setup
+ [ -n ]
+ [ -n ]
+ sleep 5
+ lxc exec autopkgtest-prepare-Due -- systemctl mask [email protected]
Created symlink '/etc/systemd/system/[email protected]' → '/dev/null'.
+ safe_reboot
+ get_boot_id
+ lxc exec autopkgtest-prepare-Due -- cat /proc/sys/kernel/random/boot_id
+ boot_id=5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ echo 5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ previous_boot_id=5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ echo Issuing reboot (current boot id: 5dfc9c60-2c1c-4157-93df-6b2c730691a6
Issuing reboot (current boot id: 5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ lxc exec autopkgtest-prepare-Due -- reboot
+ get_boot_id
+ lxc exec autopkgtest-prepare-Due -- cat /proc/sys/kernel/random/boot_id
+ boot_id=5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ echo 5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ current_boot_id=5dfc9c60-2c1c-4157-93df-6b2c730691a6
+ timeout=36
+ [ 36 -ge 0 ]
+ [ 5dfc9c60-2c1c-4157-93df-6b2c730691a6 = unknown ]
+ [ 5dfc9c60-2c1c-4157-93df-6b2c730691a6 = 5dfc9c60-2c1c-4157-93df-6b2c730691a6
]
+ sleep 5
+ timeout=35
+ get_boot_id
+ lxc exec autopkgtest-prepare-Due -- cat /proc/sys/kernel/random/boot_id
+ boot_id=5879c08d-eb42-4026-8f5a-5a79a9f865f7
+ echo 5879c08d-eb42-4026-8f5a-5a79a9f865f7
+ current_boot_id=5879c08d-eb42-4026-8f5a-5a79a9f865f7
+ [ 35 -ge 0 ]
+ [ 5879c08d-eb42-4026-8f5a-5a79a9f865f7 = unknown ]
+ [ 5879c08d-eb42-4026-8f5a-5a79a9f865f7 = 5dfc9c60-2c1c-4157-93df-6b2c730691a6
]
+ [ 35 -ge 0 ]
+ echo Reboot successful (current boot id: 5879c08d-eb42-4026-8f5a-5a79a9f865f7)
Reboot successful (current boot id: 5879c08d-eb42-4026-8f5a-5a79a9f865f7)
+ wait_booted
+ timeout=60
+ [ 60 -ge 0 ]
+ timeout=59
+ sleep 1
+ lxc exec autopkgtest-prepare-Due runlevel
+ O=unknown
+ continue
+ [ 59 -ge 0 ]
+ timeout=58
+ sleep 1
+ lxc exec autopkgtest-prepare-Due runlevel
+ O=unknown
+ continue
+ [ 58 -ge 0 ]
+ timeout=57
+ sleep 1
+ lxc exec autopkgtest-prepare-Due runlevel
+ O=unknown
+ continue
+ [ 57 -ge 0 ]
+ timeout=56
+ sleep 1
+ lxc exec autopkgtest-prepare-Due runlevel
+ O=unknown
+ continue
+ [ 56 -ge 0 ]
```
... and then it fails with this error:
```
+ continue
+ [ -1 -ge 0 ]
+ [ -1 -ge 0 ]
+ echo Timed out waiting for container to boot
Timed out waiting for container to boot
+ exit 1
+ [ -z autopkgtest-prepare-Due ]
+ lxc delete -f autopkgtest-prepare-Due
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064584
Title:
Timed out waiting for container to boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2064584/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
