The bug was not completely/properly fixed, especially not in Noble:
```
$ lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3.5; lxc exec c1 -- lxc list
Creating c1
Starting c1
Installing LXD snap, please be patient.
Traceback (most recent call last):
File "<string>", line 1, in <module>
ConnectionResetError: [Errno 104] Connection reset by peer
```
It seems to be due to snapd not being fully seeded when the `snap
install lxd` request comes in:
```
$ lxc delete -f c1; lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3.5; lxc
exec c1 -- systemctl status snapd.seeded.service; lxc exec c1 -- lxc list; lxc
exec c1 -- sh -c 'systemctl status lxd-installer@*.service'
Creating c1
Starting c1
● snapd.seeded.service - Wait until snapd is fully seeded
Loaded: loaded (/usr/lib/systemd/system/snapd.seeded.service; enabled;
preset: enabled)
Active: activating (start) since Tue 2024-06-04 20:49:32 UTC; 636ms ago
Main PID: 333 (snap)
Tasks: 6 (limit: 36997)
Memory: 13.2M (peak: 13.7M)
CPU: 550ms
CGroup: /system.slice/snapd.seeded.service
└─333 /usr/bin/snap wait system seed.loaded
Jun 04 20:49:32 c1 systemd[1]: Starting snapd.seeded.service - Wait until snapd
is fully seeded...
Installing LXD snap, please be patient.
Traceback (most recent call last):
File "<string>", line 1, in <module>
ConnectionResetError: [Errno 104] Connection reset by peer
/usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
Error: Command not found
× lxd-installer@0-411-0.service - Helper to install lxd snap on demand (PID
411/UID 0)
Loaded: loaded (/usr/lib/systemd/system/lxd-installer@.service; static)
Active: failed (Result: exit-code) since Tue 2024-06-04 20:49:33 UTC; 1min
30s ago
Duration: 240ms
TriggeredBy: ● lxd-installer.socket
Process: 414 ExecStart=/bin/sh -eux
/usr/share/lxd-installer/lxd-installer-service (code=exited, status=10)
Main PID: 414 (code=exited, status=10)
CPU: 24ms
Jun 04 20:49:33 c1 sh[416]: +
PRIVACY_POLICY_URL=https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
Jun 04 20:49:33 c1 sh[416]: + UBUNTU_CODENAME=noble
Jun 04 20:49:33 c1 sh[416]: + LOGO=ubuntu-logo
Jun 04 20:49:33 c1 sh[416]: + track=5.21
Jun 04 20:49:33 c1 sh[416]: + [ -n 24.04 ]
Jun 04 20:49:33 c1 sh[416]: + echo 5.21/stable/ubuntu-24.04
Jun 04 20:49:33 c1 sh[414]: + snap install lxd
--channel=5.21/stable/ubuntu-24.04
Jun 04 20:49:33 c1 sh[417]: error: too early for operation, device not yet
seeded or device model not acknowledged
Jun 04 20:49:33 c1 systemd[1]: lxd-installer@0-411-0.service: Main process
exited, code=exited, status=10/n/a
Jun 04 20:49:33 c1 systemd[1]: lxd-installer@0-411-0.service: Failed with
result 'exit-code'.
```
This same error can be reproduced more simply with:
```
$ lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3; lxc exec c1 -- snap
install lxd
Creating c1
Starting c1
error: too early for operation, device not yet seeded or device model not
acknowledged
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039148
Title:
lxd-installer can race or temp-fail and then block itself
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2039148/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
