tomp
June 17, 2021, 9:22am
21
esosan
June 17, 2021, 9:30am
22
I don’t understand, the server it’s not an arch386. at the moment there is no solution or workaround to gain connectivity again?
tomp
June 17, 2021, 9:32am
23
The move to core20 affected all architectures, but meant that i386 isn’t supported any more.
I’m currently looking into if there is a workaround, like we did for the lvm tools.
tomp
June 17, 2021, 9:34am
25
It seems to be an issue with snap on bionic hosts.
I have this is issue also: ubuntu host 18.04 and containers have no IP addresses this morning.
tomp
June 17, 2021, 9:50am
27
I’m tracking this over at
opened 09:09AM - 17 Jun 21 UTC
Hi,
* Distribution: Ubuntu
* Distribution version: 18.04.5 LTS (Bionic Be… aver)
* The output of "lxc info" or if that fails:
* Kernel version: 4.15.0-112-generic
* LXC version: 4.15
* LXD version: 4.15
* Storage backend in use: ceph
There might have been an update that broke the dnsmasq binary that is provided by the last lxd snap.
The 'snap start lxd' emits the following error :
lvl=eror msg="The dnsmasq process exited prematurely" driver=bridge err="Process exited with non-zero value 1" network=lxdbr0 project=default
I've dug further and here is what I did :
- nsenter -t $(cat /var/snap/lxd/common/lxd.pid) -n
- cd /snap/lxd/current/bin
- ./dnsmasq --keep-in-foreground --strict-order --bind-interfaces --except-interface=lo --pid-file= --no-ping --interface=lxdbr1 --dhcp-rapid-commit --quiet-dhcp --quiet-dhcp6 --quiet-ra --listen-address=10.124.111.1 --dhcp-no-override --dhcp-authoritative --dhcp-leasefile=/var/snap/lxd/common/lxd/networks/lxdbr1/dnsmasq.leases --dhcp-hostsfile=/var/snap/lxd/common/lxd/networks/lxdbr1/dnsmasq.hosts --dhcp-range 10.124.111.2,10.124.111.254,1h -s lxd -S /lxd/ --conf-file=/var/snap/lxd/common/lxd/networks/lxdbr1/dnsmasq.raw -u lxd -g lxd
- ./dnsmasq: error while loading shared libraries: libnettle.so.7: cannot open shared object file: No such file or directory
To my knoledge, but I admit that I don't know that much about snap, the problem resides that I have an ubuntu 18.04 that uses snap core18 and lxd-4.15 has been built against core20...
I don't know how to get lxd's dnsmasq run anymore. If anyone can help. Thanks a lot !
tomp
June 17, 2021, 9:50am
28
I reopened the original LVM issue as it would be good to try and figure out what was going on there:
opened 06:18AM - 17 Jun 21 UTC
# Required information
* Distribution: ubuntu
* Distribution version: 18… .04.4
* The output of "lxc info" or if that fails:
* Kernel version:4.15.0-144-generic
* LXC version: 4.15
* LXD version: 4.15
* Storage backend in use: LVM (xfs/no thinpool)
# Issue description
All Containers doesn't start anymore. Seems to be a LVM problem. But all PVS and VGS are present
```
Error: Failed preparing container for start: Failed to activate LVM logical volume "/dev/pool_0/containers_iceCast": Failed to run: lvchange --activate y --ignoreactivationskip /dev/pool_0/containers_iceCast: Volume group "pool_0" not found
Cannot process volume group pool_0
```
stgraber
June 17, 2021, 4:02pm
29
Conclusion is that for anyone who’s using nested LVM (VG in a LV), the change of LVM version that occurred by LXD moving from a core18 to a core20 base changed LVM’s behavior to not scanning such LVs. As having LVM perform this scan every time is quite resource intensive, we don’t want to alter the default LVM configuration to do it.
Instead anyone depending on such a setup should do snap set lxd lvm.external=true followed by systemctl reload snap.lxd.daemon. This will reconfigure the snap to rely on your system’s LVM tools and configuration rather than the snap’s.
1 Like