Thanks Stephane! I appreciate.
Michel Dubé Mégamédium Inc. Administration systèmes Linux/Unix sur environnements virtualisés (OVH - OpenStack - LXD - XenServer - AWS - RackSpace - RunAbove) Intégrateur de logiciels libres (Open Source) 514-928-4869 ++++++++++++++++++++++++++++++++++++++++++++++++= 2016-10-02 16:38 GMT-04:00 Stéphane Graber <[email protected]>: > Hi, > > Yeah, sounds like the same issue. > > The fix for this just got released in Ubuntu 16.10 and will get > automatically backported by our scripts in the next couple of hours. > > On Sun, Oct 02, 2016 at 09:30:57PM +0100, Matthew Williams wrote: > > I guess I might be seeing something similar? (I came to this list to > report > > my problem but found this thread which seems maybe related) > > > > Also on trusty, been working fine for months. Earlier today I did an > > update, and since then the lxd daemon doesn't seem to start for me: > > > > Some pastes: http://paste.ubuntu.com/23267034/ > > > > If I just run lxd from the command line "sudo lxd" > > > > I can run lxc list but I get > > $ lxc list > > Permission denied, are you in the lxd group? > > > > I am in the lxd group - however as I don't normally run lxd this way I'm > > not sure if I would expect this to work anyway > > > > On Sat, Oct 1, 2016 at 6:53 PM, Stéphane Graber <[email protected]> > wrote: > > > > > On Sat, Oct 01, 2016 at 08:03:54AM -0400, Michel Dubé wrote: > > > > Hi, > > > > > > > > I did an update ON a Trusty server: lxd and lxd-client > > > > v. 2.3-0ubuntu3~ubuntu14.04.1 OVER some version 2.2 and it failed. > > > > > > > > Error: initctl: Unknown job: lxd > > > > Error: ubuntu systemctl: command not found > > > > > > > > > > > > This VM server has been installed about 9 months ago and I have had > no > > > > problem with updates/upgrades since the beginning but today. All the > > > > updates are done regurlarly. I have 2 of them, same config, one for > > > > testing, one on production. > > > > > > > > Finally I tried to roll back to a previous version by getting the deb > > > > packages v2.2 and I did not find them. So I removed lxd and > lxd-client > > > and > > > > installed the previous available version (2.1) of deb packages. > > > > > > > > And lxd then start correctly. > > > > > > > > Is this a bug or a bad config of an old LXC/LXD system that was > running > > > > pretty well till today? > > > > > > > > Any Idea to solve this problem without switching to 16.04? > > > > > > > > Thanks! > > > > > > > > Michel > > > > > > Most likely a packaging bug in the script that does bridge > configuration > > > migration in LXD 2.3. I'll take a look at this later today or tomorrow. > > > > > > You can most likely avoid this problem by moving > /etc/default/lxd-bridge > > > out of the way and then running the upgrade again. > > > > > > Though then your existing bridge will not be converted and you'll have > > > to define it again using the new "lxc network" commands. > > > > > > > > > Sorry about that. We did rather comprehensive testing on ubuntu 16.10 > > > and 16.04, but clearly missed something with Ubuntu 14.04. > > > > > > -- > > > Stéphane Graber > > > Ubuntu developer > > > http://www.ubuntu.com > > > > > > _______________________________________________ > > > lxc-users mailing list > > > [email protected] > > > http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > _______________________________________________ > > lxc-users mailing list > > [email protected] > > http://lists.linuxcontainers.org/listinfo/lxc-users > > > -- > Stéphane Graber > Ubuntu developer > http://www.ubuntu.com > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users >
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
