LXD downgraded after installing JUJU

LXD
1

Hi all,
I had a three node LXD cluster installed on KVM virtual machines
Host and guests all have Kubuntu 18.04 updated up today
I installed LXD using SNAP to have the 3.12 version (I had problems with the 3.0.3 that comes with Kubuntu 18.04 see thread)

The cluster starts and stops correctly ending in three nodes fuly operational

Then I installed JUJU on the first node (kvmnode1) with these commands:

sudo add-apt-repository -yu ppa:juju/stable
sudo apt update
sudo apt install juju

After a reboot I see that the node no more belongs to a cluster, the cluster database is empty and the LXD version is 3.0.3

sysop@kvmnode1:~$ sudo lxc cluster list
[sudo] password di sysop:
Error: LXD server isn’t part of a cluster
sysop@kvmnode1:~$ sudo systemctl status snap.lxd.daemon
● snap.lxd.daemon.service - Service for snap application lxd.daemon
Loaded: loaded (/etc/systemd/system/snap.lxd.daemon.service; static; vendor preset: enabled)
Active: active (running) since Wed 2019-05-01 19:01:41 CEST; 3min 6s ago
Main PID: 1794 (daemon.start)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/snap.lxd.daemon.service
‣ 1794 /bin/sh /snap/lxd/10601/commands/daemon.start
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 4: fd: 11: blkio
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 5: fd: 12: hugetlb
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 6: fd: 13: cpu,cpuacct
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 7: fd: 14: perf_event
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 8: fd: 15: pids
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 9: fd: 16: rdma
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 10: fd: 17: memory
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 11: fd: 18: name=systemd
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: 12: fd: 19: unified
mag 01 19:01:45 kvmnode1 lxd.daemon[1794]: t=2019-05-01T19:01:45+0200 lvl=warn msg=“CGroup memory swap accounting is disabled, swap limits will be ignored.”
sysop@kvmnode1:~$ sudo -i
root@kvmnode1:~# echo “SELECT * FROM config” | sqlite3 /var/lib/lxd/database/local.db
root@kvmnode1:~# sudo lxd --version
3.0.3
root@kvmnode1:~#

Strangely on the other two nodes the first node seems active and the lxd version is 3.12

sysop@kvmnode2:~$ sudo lxc cluster list
[sudo] password for sysop:
±---------±----------------------------±---------±-------±------------------+
| NAME | URL | DATABASE | STATE | MESSAGE |
±---------±----------------------------±---------±-------±------------------+
| kvmnode1 | https://192.168.201.11:8443 | YES | ONLINE | fully operational |
±---------±----------------------------±---------±-------±------------------+
| kvmnode2 | https://192.168.201.12:8443 | YES | ONLINE | fully operational |
±---------±----------------------------±---------±-------±------------------+
| kvmnode3 | https://192.168.201.13:8443 | YES | ONLINE | fully operational |
±---------±----------------------------±---------±-------±------------------+
sysop@kvmnode2:~$ sudo lxd --version
3.12
sysop@kvmnode2:~

How can I install JUJU without downgrading LXD?

2

No luck even using snap install and lxd version 3.12: after a restart of the three nodes the first node not start lxd.

On the failing node I have

sysop@kvmnode1:/var/zdata$ sudo lxd --version
[sudo] password di sysop:
3.12
sysop@kvmnode1:/var/zdata$ sudo lxc cluster list
^C
sysop@kvmnode1:/var/zdata$ sudo systemctl status snap.lxd.daemon
● snap.lxd.daemon.service - Service for snap application lxd.daemon
Loaded: loaded (/etc/systemd/system/snap.lxd.daemon.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-05-05 18:05:02 CEST; 5min ago
Process: 7275 ExecStart=/usr/bin/snap run lxd.daemon (code=exited, status=1/FAILURE)
Main PID: 7275 (code=exited, status=1/FAILURE)
mag 05 18:05:02 kvmnode1 systemd[1]: snap.lxd.daemon.service: Service hold-off time over, scheduling restart.
mag 05 18:05:02 kvmnode1 systemd[1]: snap.lxd.daemon.service: Scheduled restart job, restart counter is at 47.
mag 05 18:05:02 kvmnode1 systemd[1]: Stopped Service for snap application lxd.daemon.
mag 05 18:05:02 kvmnode1 systemd[1]: snap.lxd.daemon.service: Start request repeated too quickly.
mag 05 18:05:02 kvmnode1 systemd[1]: snap.lxd.daemon.service: Failed with result ‘exit-code’.
mag 05 18:05:02 kvmnode1 systemd[1]: Failed to start Service for snap application lxd.daemon.
sysop@kvmnode1:/var/zdata$ sudo -i
root@kvmnode1:~# echo “SELECT * FROM config” | sqlite3 /var/snap/lxd/common/lxd/database/local.db
1|cluster.https_address|192.168.201.11:8443
3|core.https_address|[::]
root@kvmnode1:~#

Seems core.https_address is lost

On a working node I see:

sysop@kvmnode2:/var/zdata$ sudo -i
[sudo] password for sysop:
root@kvmnode2:~# echo “SELECT * FROM config” | sqlite3 /var/snap/lxd/common/lxd/database/local.db
1|cluster.https_address|192.168.201.12:8443
2|core.https_address|192.168.201.12:8443
root@kvmnode2:~# lxc cluster list
±---------±----------------------------±---------±--------±------------------------------------+
| NAME | URL | DATABASE | STATE | MESSAGE |
±---------±----------------------------±---------±--------±------------------------------------+
| kvmnode1 | https://192.168.201.11:8443 | YES | OFFLINE | no heartbeat since 19m15.295952309s |
±---------±----------------------------±---------±--------±------------------------------------+
| kvmnode2 | https://192.168.201.12:8443 | YES | ONLINE | fully operational |
±---------±----------------------------±---------±--------±------------------------------------+
| kvmnode3 | https://192.168.201.13:8443 | YES | ONLINE | fully operational |
±---------±----------------------------±---------±--------±------------------------------------+
root@kvmnode2:~# lxd --version
3.12
root@kvmnode2:~#

At least lxd version remains 3.12
What I’m missing to have an lxd cluster starting correctly?