3.0.3 cant join cluster on 3.0.1

Hi,
where can I get apt 3.0.1 for my cluster? Since 3.0.1 is too old for 3.0.3

Solution:
sudo apt install -y lxd=3.0.0-0ubuntu4 lxd-client=3.0.0-0ubuntu4 lxd-tools=3.0.0-0ubuntu4 criu

Please upgrade the cluster to 3.0.3, as there are a number of clustering bugs in 3.0.1 that got fixed.

– Unit lxd.service has begun starting up.
Feb 20 17:13:50 lxd3vgtult kernel: audit: type=1400 audit(1550675630.903:47): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="/usr/bin/lxc-start"
Feb 20 17:13:50 lxd3vgtult audit[26130]: AVC apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="/usr/bin/lxc-start" pid=26130 comm=“apparmor_parser”
Feb 20 17:13:50 lxd3vgtult audit[26134]: AVC apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name=“lxc-container-default” pid=26134 comm="apparmor_pars
Feb 20 17:13:50 lxd3vgtult audit[26134]: AVC apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name=“lxc-container-default-cgns” pid=26134 comm=“apparmor
Feb 20 17:13:50 lxd3vgtult audit[26134]: AVC apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name=“lxc-container-default-with-mounting” pid=26134 comm=
Feb 20 17:13:50 lxd3vgtult audit[26134]: AVC apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name=“lxc-container-default-with-nesting” pid=26134 comm=”
Feb 20 17:13:50 lxd3vgtult systemd[1]: lxd.service: Found left-over process 20069 (lxd) in control group while starting unit. Ignoring.
Feb 20 17:13:50 lxd3vgtult systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 20 17:13:50 lxd3vgtult kernel: audit: type=1400 audit(1550675630.915:48): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="lxc-container-defau
Feb 20 17:13:50 lxd3vgtult kernel: audit: type=1400 audit(1550675630.915:49): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="lxc-container-defau
Feb 20 17:13:50 lxd3vgtult kernel: audit: type=1400 audit(1550675630.915:50): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="lxc-container-defau
Feb 20 17:13:50 lxd3vgtult kernel: audit: type=1400 audit(1550675630.915:51): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name="lxc-container-defau
Feb 20 17:13:51 lxd3vgtult lxd[26135]: t=2019-02-20T17:13:51+0200 lvl=warn msg=“CGroup memory swap accounting is disabled, swap limits will be ignored.”
Feb 20 17:13:51 lxd3vgtult lxd[26135]: t=2019-02-20T17:13:51+0200 lvl=eror msg=“Failed to start the daemon: Both legacy and new local database files exists”
Feb 20 17:13:51 lxd3vgtult lxd[26135]: Error: Both legacy and new local database files exists
Feb 20 17:13:51 lxd3vgtult systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE

node upgrade fails, so for people like me that at 3 am in the morning must deploy nodes to cluster and make it work in production.

sudo apt install -y lxd=3.0.0-0ubuntu4 lxd-client=3.0.0-0ubuntu4 lxd-tools=3.0.0-0ubuntu4 criu will install good version and cluster will work

will set to hod so the other admins do not upgrade it

sudo apt-mark hold lxd=3.0.0-0ubuntu4 lxd-client=3.0.0-0ubuntu4 lxd-tools=3.0.0-0ubuntu4
lxd set on hold.
lxd-client set on hold.
lxd-tools set on hold.

I know that myself, but corporate do not care about this. To upgrade I have to pass huge check and change management. To understand correctly, to get permission to move to lxd took almost 6 months.

Since I am not programmer. I only know that versions X.X.X stands for major.minor.bugfixes how removed ability to connect to cluster of same major LTS version on apt package manager counts as good release to LTS.
Fom official page:
LTS releases are recommended for production environments as they will benefit from regular bugfix and security updates but will not see new features added or any kind of behavioral change.