[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc packages from the lxd ppa. We downgrades the wily machines to packages from wily-updates to get lxc working again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
Curtis: can you paste a log to confirm it's the same issue as Colin? It looks like some of the cgroup:mixed logic recently introduced in cgfsng (to match that of the old cgfs backend) is a bit wrong here and attempts to create a cpu/cpuset,cpuacct symlink instead of symlinking cpu to cpuset,cpuacct. Serge: can you take a look? ** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Critical ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
Serge is out today actually, I'll try to take a look. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
This is the error jenkins@wily-slave:~$ sudo lxc-start -n curtis -F ln: failed to create symbolic link ‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file system lxc-start: conf.c: run_buffer: 347 Script exited with status 1 lxc-start: conf.c: lxc_setup: 3750 failed to run mount hooks for container 'curtis'. lxc-start: start.c: do_start: 793 failed to setup the container lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 lxc-start: start.c: __lxc_start: 1286 failed to spawn 'curtis' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Attached is the log of what happened. The wily-slave host uses the lxd ppa. it has a lower priority. These packages were installed and get updates outside of regular wily-updates: sudo apt-get install --no-install-recommends lxc=2.0* lxc-templates=2.0* lxc1=2.0* python3-lxc=2.0* liblxc1=2.0* jenkins@wily-slave:~$ apt-cache policy lxc lxc: Installed: 2.0.0~rc11-0ubuntu1~ubuntu15.10.1~ppa1 Candidate: 2.0.0~rc11-0ubuntu1~ubuntu15.10.1~ppa1 Package pin: 2.0.0~rc11-0ubuntu1~ubuntu15.10.1~ppa1 Version table: *** 2.0.0~rc11-0ubuntu1~ubuntu15.10.1~ppa1 500 200 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 1.1.5-0ubuntu0.15.10.3 500 500 http://us-sw-1.joyent.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 1.1.4-0ubuntu1 500 500 http://us-sw-1.joyent.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages jenkins@wily-slave:~$ apt-cache policy lxcfs lxcfs: Installed: 2.0.0~rc6-0ubuntu1~ubuntu15.10.1~ppa1 Candidate: 2.0.0~rc6-0ubuntu1~ubuntu15.10.1~ppa1 Package pin: 2.0.0~rc6-0ubuntu1~ubuntu15.10.1~ppa1 Version table: *** 2.0.0~rc6-0ubuntu1~ubuntu15.10.1~ppa1 500 200 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 0.10-0ubuntu2.3 500 400 http://archive.ubuntu.com/ubuntu/ wily-proposed/main amd64 Packages 0.10-0ubuntu2.1 500 500 http://us-sw-1.joyent.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ wily-security/main amd64 Packages 0.10-0ubuntu2 500 500 http://us-sw-1.joyent.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages ** Attachment added: "log of starting a container" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+attachment/4603531/+files/curtis.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1559169] Re: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
Ok, cool, that confirms it's the same thing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1559169 Title: containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1559169/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
