[Touch-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS
gnome-todo 3.28.1 - same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1640180 Title: gnome-todo doesn't load CalDav task list from EDS Status in GNOME To Do: Confirmed Status in Ubuntu GNOME: New Status in evolution-data-server package in Ubuntu: Confirmed Status in gnome-todo package in Ubuntu: Triaged Bug description: Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav task list that were set through evolution. The list are still available in working in Evolution. I tried to set them up again but they didn't appear. I tried upgrading to version available in various gnome3-ppa (still 3.20.* though) and it didn't help. The bug seems to have been handled in Fedora : https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848 and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I found those while searching the web for a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-todo/+bug/1640180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752882] [NEW] Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable
Public bug reported: The bionic builds of cloud images for one of our partners fails when installing/enabling NTP in the image during livecdrootfs build: + chroot mountpoint_gce systemctl --root / enable ntp.service Synchronizing state of ntp.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp update-rc.d: error: unable to read /etc/init.d/enable On Xnox's request I am filing a bug here and assigning to him. Please let me know if you need further information. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752882 Title: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable Status in systemd package in Ubuntu: New Bug description: The bionic builds of cloud images for one of our partners fails when installing/enabling NTP in the image during livecdrootfs build: + chroot mountpoint_gce systemctl --root / enable ntp.service Synchronizing state of ntp.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp update-rc.d: error: unable to read /etc/init.d/enable On Xnox's request I am filing a bug here and assigning to him. Please let me know if you need further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
More investigation is needed. The path *does* fix the problem, but in a
way that feels like it is a side effect.
Sorry, I should have commented on this bug before.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
dpkg-reconfigure unattended-upgrades results in update-rc.d warning
that start and stop actions are no longer supported
Status in One Hundred Papercuts:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Incomplete
Bug description:
I'm trying to script a change to the automatic updating of servers,
and tried the following:
echo "debconf unattended-upgrades/enable_auto_updates boolean false" |
debconf-set-selections -
dpkg-reconfigure -fnoninteractive unattended-upgrades
The result, however, is a warning message:
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
At this point, the change I tried to make seems to be lost. To show
this in an expanded sequence:
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: true
root@brennan:/home/ubuntu# echo "debconf
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections
-
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: false
root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive
unattended-upgrades
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
get the warning message, but the change IS accepted and takes effect.
Of course, this isn't useful in a script that should be run non-
interactively. I've tried the equivalent commands to reconfigure other
packages, and they work without error message, so I believe the
problem is with unattended-upgrades, not with debconf/dpkg-
reconfigure.
This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
not tested it). It works as expected with Ubuntu 14.04. (That version,
of course, defeaults to "false" for the unattended-
upgrades/enable_auto_updates value. I've tested both with the default
"false" value and after changing it to "true," with successful runs
both times.)
Version information, as requested:
$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
*** 0.90 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
$ apt-cache policy debconf
debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
*** 1.5.58ubuntu1 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
This debdiff should fix the problem.
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1606600/+attachment/4826417/+files/unattended-debdiff.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
dpkg-reconfigure unattended-upgrades results in update-rc.d warning
that start and stop actions are no longer supported
Status in One Hundred Papercuts:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
I'm trying to script a change to the automatic updating of servers,
and tried the following:
echo "debconf unattended-upgrades/enable_auto_updates boolean false" |
debconf-set-selections -
dpkg-reconfigure -fnoninteractive unattended-upgrades
The result, however, is a warning message:
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
At this point, the change I tried to make seems to be lost. To show
this in an expanded sequence:
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: true
root@brennan:/home/ubuntu# echo "debconf
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections
-
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: false
root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive
unattended-upgrades
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
get the warning message, but the change IS accepted and takes effect.
Of course, this isn't useful in a script that should be run non-
interactively. I've tried the equivalent commands to reconfigure other
packages, and they work without error message, so I believe the
problem is with unattended-upgrades, not with debconf/dpkg-
reconfigure.
This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
not tested it). It works as expected with Ubuntu 14.04. (That version,
of course, defeaults to "false" for the unattended-
upgrades/enable_auto_updates value. I've tested both with the default
"false" value and after changing it to "true," with successful runs
both times.)
Version information, as requested:
$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
*** 0.90 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
$ apt-cache policy debconf
debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
*** 1.5.58ubuntu1 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
I *think* the root of the issue is that the assumption in debian/rules
# we do not want to run the init script in the postinst/prerm, its
# really only useful on shutdown, see Debian bug #645919
dh_installinit $@ --no-start -- stop 10 0 6 .
is wrong.
It is not only useful on shutdown but also when dpkg-reconfigure is
invoked.
As a strawman fix, I've uploaded a fixed (xenial) package to
https://launchpad.net/~tribaal/+archive/ubuntu/unattended-upgrades
It seems to fix the issue in my limited testing: running "dpkg-
reconfigure -fnoninteractive unattended-upgrades" does apply changes
passed by debconf-set-selections.
I'll attach a debdiff to this bug as well, and open a pull request
upsteam.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
dpkg-reconfigure unattended-upgrades results in update-rc.d warning
that start and stop actions are no longer supported
Status in One Hundred Papercuts:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
I'm trying to script a change to the automatic updating of servers,
and tried the following:
echo "debconf unattended-upgrades/enable_auto_updates boolean false" |
debconf-set-selections -
dpkg-reconfigure -fnoninteractive unattended-upgrades
The result, however, is a warning message:
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
At this point, the change I tried to make seems to be lost. To show
this in an expanded sequence:
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: true
root@brennan:/home/ubuntu# echo "debconf
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections
-
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: false
root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive
unattended-upgrades
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
root@brennan:/home/ubuntu# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true
* unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
get the warning message, but the change IS accepted and takes effect.
Of course, this isn't useful in a script that should be run non-
interactively. I've tried the equivalent commands to reconfigure other
packages, and they work without error message, so I believe the
problem is with unattended-upgrades, not with debconf/dpkg-
reconfigure.
This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
not tested it). It works as expected with Ubuntu 14.04. (That version,
of course, defeaults to "false" for the unattended-
upgrades/enable_auto_updates value. I've tested both with the default
"false" value and after changing it to "true," with successful runs
both times.)
Version information, as requested:
$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
*** 0.90 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
$ apt-cache policy debconf
debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
*** 1.5.58ubuntu1 500
500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
500 http://192.168.1.2//ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
On the host. Sorry for taking so long to answer, launchpad seems to have eaten my email answer... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Correction, on the host and on outer (just tried). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Adding ppa:ubuntu-lxc/daily seems to solve the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Ok, so it seems this isn't fixed after all. Following the exact steps reported in my original message result in a non-starting container (same error message) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Fix Released Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
This seems to be fixed in vivid with lxc 1.1.2: tribaal@vivid-test:~$ apt-cache policy lxc lxc: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status tribaal@vivid-test:~$ apt-cache policy lxc-templates lxc-templates: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
So, the new lxcfs in vivid-proposed does *not* solve this particular problem. Again, running the daily PPA code solved this, but that means using the ppa for both vivid and trusty, not just vivid. Don't hesitate to let me know how I can test more/further versions of LXC, including git branches, if needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Description changed: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - - sudo su - - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config + - sudo su + - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to:
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu- lxc/daily, the tested scenario works. sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and at leas the outer guest (trusty). N.b. Only works if both the host and the first guest run the ppa code - seems like only the host running the newest code doesn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Oh, good to hear. Can I easily test what's in vivid-proposed, and/or somehow influence the landing? Since I have a pretty good test set up for this particular scenario I might as well help you guys :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: New Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436723] [NEW] Regression: Nested LXC is broken on Vivid
Public bug reported: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: New Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
