*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
I can affirm that systemd-resolved is not getting its config from
netplan, nor does adding the nameserver in /etc/systemd/resolved.conf
have any affect. The only temporary fix is modification of
/etc/resolv.
I'm seeing snapd stall on boot of generic ubuntu:22.04 images via lxd.
root@linuxtest2:~# systemctl list-jobs
JOB UNIT TYPE STATE
151 cloud-config.service start waiting
133 snapd.seeded.service start running
148 cloud-init.target
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
lxd:
Installed: 3.0.3-0ubuntu1~18.04.1
Candidate: 3.0.3-0ubuntu1~18.04.1
Version table:
*** 3.0.3-0ubuntu1~18.04.1 500
500 http://archive.ubuntu.com/ubuntu bi
I'm seeing the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780319
Title:
openssl des3 decryption fails in 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.n
I'd like to add that I've replicated this issue twice. The resolution
of adding specific listeners to maas's bind works temporarily, but we
need a way to have maas specify the listeners in bind by network
address/network by default. Restarting maas resets the bind settings
and the issue with lxd-