[Bug 1551150] Re: devel-proposed - android lxc container fails to start
/proc/cgroups #subsys_namehierarchy num_cgroups enabled debug 0 1 1 cpu 0 1 1 cpuacct 0 1 1 freezer 0 1 1 /proc/self/cgroup is empty There is no /var/log/upstart/cgroup-lite.log file and I verified that the upstart job cgroup-lite starts. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
And the content of fstab /system/etc # cat fstab # override the forced fsck from /lib/init/fstab, we use a bindmount which confuses mountall /dev/root / rootfs defaults0 0 # swap file /SWAP.swap noneswapsw 0 0 -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Ondrej Kubik (w-ondra) -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
android container log with cgroup-lite installed and content of mountinfo from the same boot. ** Attachment added: "mountinfo.out" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584668/+files/mountinfo.out -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
And syslog ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584669/+files/syslog -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
The phone uses upstart. I'll try to get the content of mountinfo -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
With cgroup-lite install the error message is different: lxc-start 20160229153538.890 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - cgroupfs failed to detect cgroup metadata lxc-start 20160229153538.890 ERRORlxc_start - start.c:lxc_spawn:1026 - failed initializing cgroup support lxc-start 20160229153538.891 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 20160229160049.670 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:874 - Could not find writable mount point for cgroup hierarchy 7 while trying to create cgroup. lxc-start 20160229160049.671 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuacct/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/debug/ lxc-start 20160229160049.672 ERRORlxc_start - start.c:lxc_spawn:1033 - failed creating cgroups lxc-start 20160229160049.673 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
I installed cgroup-lite 1.10 but it still doesn't boot. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
cgroup-lite is not installed: un cgroup-lite ii systemd:armhf 229-1ubuntu4 I cannot paste the content of /proc/mounts because I only have adb in recovery (the devices fails before adb starts otherwise) -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
dmesg from a system that doesn't boot. ** Attachment added: "dmesg.out" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551150/+attachment/4584338/+files/dmesg.out ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. + + Device tarballs between 446 and 447 are the same. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
~ # cat /data/system-data/var/log/lxc/android.log lxc-start 20160229125348.090 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - cgroupfs failed to detect cgroup metadata lxc-start 20160229125348.091 ERRORlxc_start - start.c:lxc_spawn:1026 - failed initializing cgroup support lxc-start 20160229125348.091 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229125348.091 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229125348.092 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. ** Summary changed: - devel-proposed doesn't boot + devel-proposed - android lxc container fails to start ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 - ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on - other devices do not boot and hang on the boot logo. + ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent + images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium - * New upstream release (2.0.0~rc3) - - Make the cgfs backend and cgns work without cgmanager - - Manpage updates - - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) - * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral + * New upstream release (2.0.0~rc3) + - Make the cgfs backend and cgns work without cgmanager + - Manpage updates + - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) + * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium - * Use versioned dependencies against the various binary packages. - * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) - * Move the lxcfs recommends from lxc-templates to liblxc1. - * Drop cgmanager, use the cgfs backend instead. - * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. + * Use versioned dependencies against the various binary packages. + * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) + * Move the lxcfs recommends from lxc-templates to liblxc1. + * Drop cgmanager, use the cgfs backend instead. + * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 + + Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. -- 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/1551150 Title: devel-proposed doesn't boot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
changes list between 446 and 447. ** Attachment added: "446-447.changes" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584311/+files/446-447.changes ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: - ubuntu-touch/devel-proposed/krillin.en/mako/ 338 and equivalent images - on other devices do not boot and hang on the boot logo. + Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 + + ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on + other devices do not boot and hang on the boot logo. ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on other devices do not boot and hang on the boot logo. + + From the list of changes, it could be lxc: + 446: lxc 2.0.0~rc2-0ubuntu2 + 447: lxc 2.0.0~rc3-0ubuntu1 ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 + + lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium + + * New upstream release (2.0.0~rc3) + - Make the cgfs backend and cgns work without cgmanager + - Manpage updates + - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) + * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral + + lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium + + * Use versioned dependencies against the various binary packages. + * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) + * Move the lxcfs recommends from lxc-templates to liblxc1. + * Drop cgmanager, use the cgfs backend instead. + * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. -- 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/1551150 Title: devel-proposed doesn't boot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1526264] Re: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16)
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1526264] [NEW] ntpdate fails with invalid argument when device is set to a date in the future
Public bug reported: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument = Workaround = Use option -b root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec ** Affects: canonical-devices-system-image Importance: High Status: New ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Also affects: ntp (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Description changed: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument + + = Workaround = + Use option -b + + root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' + mercredi 16 décembre 2015, 13:00:00 (UTC+0100) + root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com + 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1526264] Re: ntpdate fails with invalid argument when device is set to a date in the future
** Description changed: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument + After some experimentation, ntpdate fails if the difference between the + current time on the device and the real time is bigger than 2^16 (65536) + = Workaround = - Use option -b + Use option -b root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec ** Summary changed: - ntpdate fails with invalid argument when device is set to a date in the future + ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- 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/1516971 Title: LXC's preserve_ns fails on < 3.8 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+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 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
It is also affecting devel-proposed phone images cf bug 1516971 -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1516037/+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 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
I confirm that the phone boots successfully after downgrading liblxc1, lxc and python3-lxc to version 1.1.4-0ubuntu3 ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+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 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
** This bug is no longer a duplicate of bug 1516037 lxc-start fails with 1.1.5-0ubuntu1 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+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 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- 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/1508744 Title: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+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 1394919] Re: constant crash in trying to collect info for recoverable error of cgmanager
Here are all the logs you requested. The first dbus-send command hangs and the second works. Perhaps it is a coincidence but the problem seems to be triggered when the systems running out of memory, killed webapp-container and tries to restore gmail webapp (or maybe any other webapp) In syslog webapp-container is killed at Nov 25 08:24:23 ubuntu-phablet kernel: [16138.987397]Killing 'webapp-containe' (23587), adj 900, It almost match with the time of the apport crash (symptom of this bug) $ grep ^Date /var/crash/_usr_share_apport_recoverable_problem.32011.crash Date: Tue Nov 25 08:24:50 2014 ** Attachment added: 20141125_1394919_logs.tgz https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+attachment/4267492/+files/20141125_1394919_logs.tgz ** Summary changed: - constant crash in trying to collect info for recoverable error of cgmanager + cgproxy hangs ** Changed in: cgmanager (Ubuntu) Importance: Undecided = Critical ** Changed in: apport (Ubuntu) Status: Confirmed = Invalid ** Changed in: apport (Ubuntu RTM) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1394919 Title: cgproxy hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+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 1394919] Re: cgproxy hangs
*** This bug is a duplicate of bug 1377332 *** https://bugs.launchpad.net/bugs/1377332 I'm marking this report as duplicate of 1377332 since this is the original issue and apport was the symptom. I created bug 1396160 for apport specific issue. ** This bug has been marked a duplicate of bug 1377332 [TOPBLOCKER] UI randomly freezes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1394919 Title: cgproxy hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+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 1306575] [NEW] package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrade test from Precise AMD64 to Trusty with nearly all of main installed. Note that nova.conf has not been manually modified before upgrade. From apt-term.log: Setting up nova-common (1:2014.1~rc2-0ubuntu1) ... Installing new version of config file /etc/logrotate.d/nova-manage ... Installing new version of config file /etc/nova/api-paste.ini ... Installing new version of config file /etc/nova/policy.json ... Installing new version of config file /etc/nova/nova.conf ... Installing new version of config file /etc/sudoers.d/nova_sudoers ... Command failed, please check log for more info 2014-04-11 12:03:57.516 57962 CRITICAL nova [-] KeyError: VerNum(83) 2014-04-11 12:03:57.516 57962 TRACE nova Traceback (most recent call last): 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/bin/nova-manage, line 10, in module 2014-04-11 12:03:57.516 57962 TRACE nova sys.exit(main()) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/cmd/manage.py, line 1374, in main 2014-04-11 12:03:57.516 57962 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/cmd/manage.py, line 883, in sync 2014-04-11 12:03:57.516 57962 TRACE nova return migration.db_sync(version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/migration.py, line 29, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return IMPL.db_sync(version=version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.py, line 44, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return versioning_api.upgrade(get_engine(), repository, version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 186, in upgrade 2014-04-11 12:03:57.516 57962 TRACE nova return _migrate(url, repository, version, upgrade=True, err=err, **opts) 2014-04-11 12:03:57.516 57962 TRACE nova File string, line 2, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py, line 159, in with_engine 2014-04-11 12:03:57.516 57962 TRACE nova return f(*a, **kw) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 345, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova changeset = schema.changeset(version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 80, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changeset = self.repository.changeset(database, start_ver, version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/repository.py, line 225, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changes = [self.version(v).script(database, op) for v in versions] 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/repository.py, line 189, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions.version(*p, **k) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/version.py, line 155, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions[VerNum(vernum)] 2014-04-11 12:03:57.516 57962 TRACE nova KeyError: VerNum(83) 2014-04-11 12:03:57.516 57962 TRACE nova dpkg: error processing package nova-common (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 12:03:58 2014 DuplicateSignature: package:nova-common:1:2014.1~rc2-0ubuntu1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: nova Title: package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-04-11 (0 days ago) mtime.conffile..etc.nova.nova.conf: 2014-04-11T12:03:56.317961 ** Affects: nova (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-package rls-t-incoming trusty uec-images ** Description changed: - Upgrade test from Precise AMD64 to Trusty + Upgrade test from Precise AMD64 to Trusty with nearly all of main + installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu
[Bug 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
I'm reopening this report, it is still an issue with krb5 1.12+dfsg- 2ubuntu3 ** Changed in: krb5 (Ubuntu Trusty) Status: Fix Released = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
New apt.log for P-T upgrade See also bug 1304702 for an upgrade with the same failure from S to T ** Attachment added: apt_krb5_1.12+dfsg-2ubuntu3.log https://bugs.launchpad.net/ubuntu/trusty/+source/krb5/+bug/1304403/+attachment/4076761/+files/apt_krb5_1.12%2Bdfsg-2ubuntu3.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304403] Re: Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist
** Also affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist + Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1267367] [NEW] lxc-create shouldn't create container when template is called with --help argument
Public bug reported: When option --help is passed as template argument, lxc-create creates the base directory structure of the container. Then next call to lxc- create with the same name will fail because the container already exists. TEST CASE: 1. $ sudo lxc-create -n test--help -t ubuntu -- -h [...] output of lxc-ubuntu -h [...] $ sudo lxc-create -n test--help -t ubuntu -- -a amd64 Container already exists EXPECTED RESULT Container is not created and another call to lxc-create with the same name can be executed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta1-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 9 09:19:01 2014 SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2012-01-31 (708 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug trusty ** Description changed: When option --help is passed as template argument, lxc-create creates the base directory structure of the container. Then next call to lxc- create with the same name will fail because the container already exists. TEST CASE: 1. $ sudo lxc-create -n test--help -t ubuntu -- -h [...] output of lxc-ubuntu -h [...] $ sudo lxc-create -n test--help -t ubuntu -- -a amd64 Container already exists EXPECTED RESULT - Container is not create and another call to lxc-create with the same name can be executed. + Container is not created and another call to lxc-create with the same name can be executed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta1-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 9 09:19:01 2014 SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2012-01-31 (708 days ago) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up -- 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/1267367 Title: lxc-create shouldn't create container when template is called with --help argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 1267367] Re: lxc-create shouldn't create container when template is called with --help
** Summary changed: - lxc-create shouldn't create container when template is called with --help argument + lxc-create shouldn't create container when template is called with --help -- 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/1267367 Title: lxc-create shouldn't create container when template is called with --help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 1267367] Re: lxc-create shouldn't create container when template is called with --help
test--help is the name of the container, it is just a bad name. Sorry for the confusion. You can try with lxc-create -n lp1267367 -t ubuntu -- -h or any name. ** Changed in: lxc (Ubuntu) Status: Incomplete = 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/1267367 Title: lxc-create shouldn't create container when template is called with --help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 1244910] Re: dep8 test failed: missing test dependency '@'
** Changed in: cherrypy3 (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cherrypy3 in Ubuntu. https://bugs.launchpad.net/bugs/1244910 Title: dep8 test failed: missing test dependency '@' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cherrypy3/+bug/1244910/+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 1212444] [NEW] cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14
Public bug reported: During the provisioning of a local VM with cloud-init and parted 2.3.14, cc_growpart fails in auto grow mode with the following error: === 2013-08-14 08:07:02,117 - util.py[DEBUG]: Running command ['parted', 'resizepart', '/dev/vda', '1'] with allowed return codes [0] (shell=False, capture=True) 2013-08-14 08:07:02,139 - cc_growpart.py[DEBUG]: '/' FAILED: failed to resize: disk=/dev/vda, ptnum=1: Unexpected error while running command. Command: ['parted', 'resizepart', '/dev/vda', '1'] Exit code: 1 Reason: - Stdout: '\r \rError: Could not stat device resizepart - No such file or directory.\n' Stderr: '' === /dev/vda1 is not resized to use entire disk space and limited to 2GB. Run #90 on the 12th is successful with previous version of parted. Full log attached and online at [1] [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- setup-testbed/ARCH=amd64,label=albali/91/console ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cloud-init (not installed) ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 23:09:56 2013 InstallationDate: Installed on 2012-10-25 (293 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: cloud-init UpgradeStatus: Upgraded to saucy on 2012-12-02 (255 days ago) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: consoleText https://bugs.launchpad.net/bugs/1212444/+attachment/3773061/+files/consoleText -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212444 Title: cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1212444/+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 1198833] [NEW] autopkgtest does not stop until service pygopherd is stopped or killed
Public bug reported: pygopherd is installed and started during autopkgtest of squid3 [1] as part of the test depedencies. But the run never ends until pygopherd is stopped/killed. The service should ever be stopped as part of the test cleanup, or autopkgtest should kill all the remaining children when all the tests are done. [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- squid3/22/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: squid3 3.1.20-1ubuntu7 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 8 10:22:26 2013 MarkForUpload: True SourcePackage: squid3 UpgradeStatus: Upgraded to saucy on 2012-01-31 (523 days ago) modified.conffile..etc.squid3.squid.conf: [modified] mtime.conffile..etc.squid3.squid.conf: 2012-08-07T15:04:05.743610 ** Affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: - pygopherd is installed and started during autopkgtest of squid3 as part - of the test depedencies. But the run never ends until pygopherd is + pygopherd is installed and started during autopkgtest of squid3 [1] as + part of the test depedencies. But the run never ends until pygopherd is stopped/killed. The service should ever be stopped as part of the test cleanup, or autopkgtest should kill all the remaining children when all the tests are done. + + [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- + squid3/22/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: squid3 3.1.20-1ubuntu7 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 8 10:22:26 2013 MarkForUpload: True SourcePackage: squid3 UpgradeStatus: Upgraded to saucy on 2012-01-31 (523 days ago) modified.conffile..etc.squid3.squid.conf: [modified] mtime.conffile..etc.squid3.squid.conf: 2012-08-07T15:04:05.743610 ** Also affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Summary changed: - autopkgtest do not stop until pygopherd is killed + autopkgtest do not stop until service pygopherd is stopped or killed ** Summary changed: - autopkgtest do not stop until service pygopherd is stopped or killed + autopkgtest does not stop until service pygopherd is stopped or killed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1198833 Title: autopkgtest does not stop until service pygopherd is stopped or killed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1198833/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
I'm reopening because I can reproduce it on different hardware, but it doesn't fail when running the same command twice and it seems a bit racy. I'm searching for a way to reliably reproduce that problem. ** Changed in: lxc (Ubuntu) Status: Invalid = Confirmed ** Changed in: lxc (Ubuntu) Status: Confirmed = Incomplete -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
This is reproducible on several systems, but only the 1rst time I start a container when /sys/fs/cgroup/devices/lxc/NAME/ doesn't already exist. -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724404/+files/RelatedPackageVersions.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxc.default.txt
apport information ** Attachment added: lxc.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724406/+files/lxc.default.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
apport information ** Tags added: apparmor apport-collected ** Description changed: With kernel 3.10.0 lxc-create fails with the following error: lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012' is setup. lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called for subsys devices name lxc/saucy-i386-20130701-1012 lxc-start 1372673552.852 DEBUGlxc_cgroup - using cgroup mounted at '/sys/fs/cgroup/devices' lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: returning /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012 for subsystem devices.deny lxc-start 1372673552.852 ERRORlxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument lxc-start 1372673552.852 ERRORlxc_conf - Error setting devices.deny to a for lxc/saucy-i386-20130701-1012 Second run of lxc-start works fine. Downgrading to 3.9.0-7 fixes the issue. The rootfs of the container is a loop-mounted squashfs from a loop- mounted ISO of latest saucy desktop image. pre-start, pre-mount, post-stop, lxc config and fstab attached ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 1 14:26:35 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (516 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up + --- + ApportVersion: 2.10.2-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2012-10-25 (251 days ago) + InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) + MarkForUpload: True + Package: lxc 0.9.0-0ubuntu16 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 + Tags: saucy apparmor + Uname: Linux 3.10.0-2-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) + UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724402/+files/Dependencies.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
With otto from lp:otto I can reproduce the problem with the command: $ sudo ./bin/otto -d create -u lp1196518-$RANDOM ~/iso/ubuntu/saucy-desktop-amd64.iso The write(fd, value, strlen(value)) in do_cgroup_set in cgroup.c fails with Invalid Argument If the command is executed a second time with the same container name (replace $RANDOM by the number generated previoulsly), it works fine. -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxc-net.default.txt
apport information ** Attachment added: lxc-net.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724405/+files/lxc-net.default.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724403/+files/KernLog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxcsyslog.txt
apport information ** Attachment added: lxcsyslog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724407/+files/lxcsyslog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
For the moment, the workaround is to remove lxc.cgroup.devices.deny from the config file, which is okay in our case since the machines are just test hosts, but is not in the general case. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: bot-stop-nagging -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724623/+files/KernLog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724626/+files/ProcCpuinfo.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724622/+files/IwConfig.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724620/+files/CurrentDmesg.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
apport information ** Description changed: With kernel 3.10.0 lxc-create fails with the following error: lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012' is setup. lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called for subsys devices name lxc/saucy-i386-20130701-1012 lxc-start 1372673552.852 DEBUGlxc_cgroup - using cgroup mounted at '/sys/fs/cgroup/devices' lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: returning /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012 for subsystem devices.deny lxc-start 1372673552.852 ERRORlxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument lxc-start 1372673552.852 ERRORlxc_conf - Error setting devices.deny to a for lxc/saucy-i386-20130701-1012 Second run of lxc-start works fine. Downgrading to 3.9.0-7 fixes the issue. The rootfs of the container is a loop-mounted squashfs from a loop- mounted ISO of latest saucy desktop image. pre-start, pre-mount, post-stop, lxc config and fstab attached ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 1 14:26:35 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (516 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up --- ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-10-25 (251 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True Package: lxc 0.9.0-0ubuntu16 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Tags: saucy apparmor Uname: Linux 3.10.0-2-generic x86_64 UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up + --- + ApportVersion: 2.10.2-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=9661ff9a-af2b-4768-a741-0a313db5b763 + InstallationDate: Installed on 2012-10-25 (251 days ago) + InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) + MachineType: ASUSTeK Computer Inc. U3SG + MarkForUpload: True + Package: lxc 0.9.0-0ubuntu16 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: saucy saucy apparmor + Uname: Linux 3.10.0-2-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) + UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + dmi.bios.date: 01/28/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 305 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: U3SG + dmi.board.vendor: ASUSTeK Computer Inc. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK Computer Inc. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr305:bd01/28/2008:svnASUSTeKComputerInc.:pnU3SG:pvr1.0:rvnASUSTeKComputerInc.:rnU3SG:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: + dmi.product.name: U3SG + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK Computer Inc. ** Attachment added: AlsaInfo.txt
[Bug 1196518] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724618/+files/BootDmesg.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724625/+files/Lsusb.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724619/+files/CRDA.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724621/+files/Dependencies.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724624/+files/Lspci.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724631/+files/UdevDb.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724628/+files/ProcModules.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724632/+files/UdevLog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] lxc-net.default.txt
apport information ** Attachment added: lxc-net.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724634/+files/lxc-net.default.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724630/+files/RfKill.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724633/+files/WifiSyslog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] lxcsyslog.txt
apport information ** Attachment added: lxcsyslog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724636/+files/lxcsyslog.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724627/+files/ProcInterrupts.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] lxc.default.txt
apport information ** Attachment added: lxc.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724635/+files/lxc.default.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724629/+files/RelatedPackageVersions.txt -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
Here is a minimal test case to reproduce the problem:
NAME=test-deny-${RANDOM}
echo lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups /tmp/${NAME}.lxc
lxc-create -t ubuntu -n $NAME -f /tmp/${NAME}.lxc -- -r saucy
lxc-start -n $NAME
From what I understand, setting devices.deny or .allow = a is forbidden in
3.10 when a cgroup has children. And the hook mountcgroup creates a child
called NAME.real.
This line comes from a default configuration file in raring.
This is a change in behavior between 3.9 and 3.10 and a bit confusing.
Feel free to close if you think it is not a bug.
--
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/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - write
/sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument
with kernel 3.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: fstab https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720321/+files/fstab -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: pre-mount.sh https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720323/+files/pre-mount.sh -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: config https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720320/+files/config -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: post-stop.sh https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720322/+files/post-stop.sh -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] [NEW] lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
Public bug reported: With kernel 3.10.0 lxc-create fails with the following error: lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012' is setup. lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called for subsys devices name lxc/saucy-i386-20130701-1012 lxc-start 1372673552.852 DEBUGlxc_cgroup - using cgroup mounted at '/sys/fs/cgroup/devices' lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: returning /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012 for subsystem devices.deny lxc-start 1372673552.852 ERRORlxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument lxc-start 1372673552.852 ERRORlxc_conf - Error setting devices.deny to a for lxc/saucy-i386-20130701-1012 Second run of lxc-start works fine. Downgrading to 3.9.0-7 fixes the issue. The rootfs of the container is a loop-mounted squashfs from a loop- mounted ISO of latest saucy desktop image. pre-start, pre-mount, post-stop, lxc config and fstab attached ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 1 14:26:35 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (516 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: saucy-i386-20130701-1012.log.broken https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720325/+files/saucy-i386-20130701-1012.log.broken -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
** Attachment added: pre-start.sh https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720324/+files/pre-start.sh -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1124384] Re: Configuration reload clears event that others jobs may be waiting on
I confirm the regression in upstart 1.8-0ubuntu1.1 in Raring which also exists in 1.8-0ubuntu7 in Saucy caused by a typo in upstart.postinst: 83 elif dpkg --compare-version $UPSTART_VERSION_RUNNING ge 1.6.1; then The right option is --compare-versions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+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 1181136] [NEW] Empty log file when a container is started with the API
Public bug reported: When a container is started with the python API the log file /var/log/lxc/NAME.log is empty. This is pretty annoying to debug pre- start hook issues for example. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 ApportVersion: 2.10.1-0ubuntu1 Architecture: amd64 Date: Fri May 17 10:31:44 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (471 days ago) lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1181136 Title: Empty log file when a container is started with the API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1181136/+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 1179202] Re: fails to login with error fatal: monitor_read: unsupported request: 144
Confirmed on Saucy with openssh 6.2p1-2 ** Changed in: openssh (Ubuntu) Importance: Undecided = Critical ** Changed in: openssh (Ubuntu) Assignee: (unassigned) = Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1179202 Title: fails to login with error fatal: monitor_read: unsupported request: 144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1179202/+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 1161827] Re: lxc-start-ephemeral: non-existent option '-n' documented in man page.
Fixed in 0.9.0-0ubuntu1 ** Changed in: lxc (Ubuntu) Status: Fix Committed = Fix Released -- 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/1161827 Title: lxc-start-ephemeral: non-existent option '-n' documented in man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1161827/+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 1161827] [NEW] lxc-start-ephemeral: non-existent option '-n' documented in man page.
Public bug reported:
In the man page of lxc-start-ephemeral the option '-n' is documented:
SYNOPSIS
lxc-start-ephemeral [-o] [-n] [-d] [--bdir] [--user] [--key]
[--union-type] [--keep-data] [COMMAND]
[...]
[-n] Name of the ephemeral container (defaults to a random suffix).
But this option is not recognized by the binary:
$ sudo lxc-start-ephemeral -o pristine-raring-amd64 -n
adt-raring-amd64-tabix-20130329120215 -kd
usage: lxc-start-ephemeral [-h] [--lxcpath PATH] --orig ORIG [--bdir BDIR]
[--user USER] [--key KEY] [--daemon]
[--union-type {overlayfs,aufs}] [--keep-data]
[CMD [CMD ...]]
lxc-start-ephemeral: error: unrecognized arguments: -n
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0~rc1-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Fri Mar 29 12:02:53 2013
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2012-01-31 (422 days ago)
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apparmor apport-bug qa-manual-testing raring
--
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/1161827
Title:
lxc-start-ephemeral: non-existent option '-n' documented in man page.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1161827/+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 1160360] Re: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
Moving to flash-kernel LXC do not rootfs modifications from the templates. The proposed fix in attached branch do the equivalent of then environment variable FLASH_KERNEL_SKIP and skips flash-kernel run inside LXC container by checking the result of 'running-in-container' ** Package changed: lxc (Ubuntu) = flash-kernel (Ubuntu) ** Changed in: flash-kernel (Ubuntu) Importance: Undecided = High ** Changed in: flash-kernel (Ubuntu) Status: New = Triaged -- 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/1160360 Title: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash- kernel: 214: /usr/sbin/flash-kernel: mkimage: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1160360/+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 1158465] Re: [SRU] update Windows Azure WALinuxAgent to 1.3.2 (12.04.2, 12.10 and 13.04)
** Also affects: walinuxagent (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Quantal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1158465 Title: [SRU] update Windows Azure WALinuxAgent to 1.3.2 (12.04.2, 12.10 and 13.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1158465/+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 1159817] Re: python module lxc failed to import on ARM with: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte
BTW if you don't have a board to reproduce this issue, it is also reproducible in an armhf container created with: $ sudo lxc-create -n raring-arm -t ubuntu -- -r raring -a armhf then install python3-lxc into this container -- 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/1159817 Title: python module lxc failed to import on ARM with: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159817/+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 1160360] [NEW] flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
Public bug reported: Raring armv7l lxc: 0.9.0~rc1-0ubuntu1 flash-kernel: 3.0~rc.4ubuntu29 initramfs-tools: 0.103ubuntu0.7 When the kernel is upgraded inside an armhf LXC container running on armv7l, the upgrade fails with: === Setting up initramfs-tools (0.103ubuntu0.7) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.8.0-14-generic flash-kernel: installing version 3.8.0-14-generic Generating kernel u-boot image... /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 127 dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools === TEST CASE: 1. Install an armhf container on an arm host 2. Upgrade initramfs-tools ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 Date: Tue Mar 26 14:09:34 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-01-31 (419 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug qa-daily-testing raring -- 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/1160360 Title: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash- kernel: 214: /usr/sbin/flash-kernel: mkimage: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1160360/+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 1160360] Re: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
It is even more annoying because if you specify apt_upgrade: true in a cloud-config script and there is a package that triggers kernel hooks, then it breaks the provisioning of the lxc guest. -- 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/1160360 Title: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash- kernel: 214: /usr/sbin/flash-kernel: mkimage: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1160360/+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 1160360] Re: flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
it breaks even without that directive.
Another test case to run on a day with a package upgrade that will run
kernel hooks
1. Create the user-data file with the following content:
88888
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
ssh_authorized_keys:
- SOMEPUBKEY
apt_sources:
- source: deb http://archive.ubuntu.com/ubuntu raring restricted multiverse
- source: deb-src http://archive.ubuntu.com/ubuntu raring restricted multiverse
byobu_by_default: system
packages:
- eatmydata
- autopkgtest
- dpkg-dev
- pbuilder
- bzr
runcmd:
- [sh, -xc, echo '127.0.1.1 autopkgtest' /etc/hosts ]
88888
2. On an ARM host provision an LXC guest with the command (replace user-data by
the path to the user-data file you created above)
$ sudo lxc-create -n raring-armhf-20130326_094008 -t ubuntu-cloud -- -r
raring -a armhf -s daily -u user-data -T
https://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-armhf-root.tar.gz
3. Start the container and wait
$ sudo lxc-start -n raring-armhf-20130326_09400
--
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/1160360
Title:
flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-
kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1160360/+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 1160462] [NEW] Don't run resizefs hook during installation of an LXC container with cloud-init
Public bug reported:
Raring AMD64
cloud-init 0.7.2~bzr795-0ubuntu1
During the provisioning of an LXC guest with the template ubuntu-cloud,
cloud-init executes the hook resizefs and fails with:
2013-03-26 15:11:09,545 - util.py[DEBUG]: Running resizefs (module
'cloudinit.config.cc_resizefs' from
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_resizefs.pyc') failed
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 553, in
_run_modules
cc.run(run_name, mod.handle, func_args, freq=freq)
File /usr/lib/python2.7/dist-packages/cloudinit/cloud.py, line 63, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
File /usr/lib/python2.7/dist-packages/cloudinit/helpers.py, line 197, in run
results = functor(*args)
File /usr/lib/python2.7/dist-packages/cloudinit/config/cc_resizefs.py, line
78, in handle
if not stat.S_ISBLK(os.stat(devpth).st_mode):
OSError: [Errno 2] No such file or directory: '/dev/sdb1'
It shouldn't try to resize the hard drive and there should be an error
handler in the code.
TEST CASE:
1. Create a user-data file with the following content:
88888
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
ssh_authorized_keys:
- SOMEPUBKEY
apt_sources:
- source: deb http://archive.ubuntu.com/ubuntu raring restricted multiverse
- source: deb-src http://archive.ubuntu.com/ubuntu raring restricted multiverse
byobu_by_default: system
packages:
- eatmydata
- autopkgtest
- dpkg-dev
- pbuilder
- bzr
runcmd:
- [sh, -xc, echo '127.0.1.1 autopkgtest' /etc/hosts ]
88888
2. On an AMD64 host provision an LXC guest with the command (replace user-data
by the path to the user-data file you created above)
$ sudo lxc-create -n raring-armhf-20130326 -t ubuntu-cloud -- -r raring -a
amd64 -s daily -u user-data
3. Start the container and wait
$ sudo lxc-start -n raring-armhf-20130326
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: cloud-init (not installed)
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu4
Architecture: amd64
Date: Tue Mar 26 17:06:46 2013
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: Upgraded to raring on 2012-01-31 (419 days ago)
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug qa-manual-testing raring
** Description changed:
Raring AMD64
cloud-init 0.7.2~bzr795-0ubuntu1
During the provisioning of an LXC guest with the template ubuntu-cloud,
cloud-init executes the hook resizefs and fails with:
2013-03-26 15:11:09,545 - util.py[DEBUG]: Running resizefs (module
'cloudinit.config.cc_resizefs' from
'/usr/lib/python2.7/dist-packages/cloudinit/config/cc_resizefs.pyc') failed
Traceback (most recent call last):
- File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 553, in
_run_modules
- cc.run(run_name, mod.handle, func_args, freq=freq)
- File /usr/lib/python2.7/dist-packages/cloudinit/cloud.py, line 63, in run
- return self._runners.run(name, functor, args, freq, clear_on_fail)
- File /usr/lib/python2.7/dist-packages/cloudinit/helpers.py, line 197, in
run
- results = functor(*args)
- File /usr/lib/python2.7/dist-packages/cloudinit/config/cc_resizefs.py,
line 78, in handle
- if not stat.S_ISBLK(os.stat(devpth).st_mode):
+ File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 553, in
_run_modules
+ cc.run(run_name, mod.handle, func_args, freq=freq)
+ File /usr/lib/python2.7/dist-packages/cloudinit/cloud.py, line 63, in run
+ return self._runners.run(name, functor, args, freq, clear_on_fail)
+ File /usr/lib/python2.7/dist-packages/cloudinit/helpers.py, line 197, in
run
+ results = functor(*args)
+ File /usr/lib/python2.7/dist-packages/cloudinit/config/cc_resizefs.py,
line 78, in handle
+ if not stat.S_ISBLK(os.stat(devpth).st_mode):
OSError: [Errno 2] No such file or directory: '/dev/sdb1'
- It shouldn't try to resize the hard drive
+ It shouldn't try to resize the hard drive and there should be an error
+ handler in the code.
TEST CASE:
1. Create a user-data file with the following content:
88888
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
ssh_authorized_keys:
- - SOMEPUBKEY
+ - SOMEPUBKEY
- apt_sources:
- - source: deb http://archive.ubuntu.com/ubuntu raring restricted multiverse
- - source: deb-src http://archive.ubuntu.com/ubuntu raring restricted
multiverse
+ apt_sources:
+ - source: deb http://archive.ubuntu.com/ubuntu raring restricted multiverse
+ - source: deb-src
[Bug 1159817] [NEW] python module lxc failed to import on ARM with: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte
Public bug reported: Raring ARM python3-lxc: 0.9.0~rc1-0ubuntu1 On ARM python3 module lxc failed to import. This breaks commands like lxc-ls TEST CASE: 1. On an ARM device run the following command: $ python3 -c import lxc ACTUAL RESULT: $ python3 -c import lxc Traceback (most recent call last): File string, line 1, in module File /usr/lib/python3/dist-packages/lxc/__init__.py, line 24, in module import _lxc UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python3-lxc 0.9.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu3 Architecture: amd64 Date: Mon Mar 25 15:35:25 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-01-31 (418 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug qa-manual-testing raring ** Description changed: Raring ARM python3-lxc: 0.9.0~rc1-0ubuntu1 - On ARM python3 module lxc failed to import. + On ARM python3 module lxc failed to import. This breaks commands like + lxc-ls TEST CASE: 1. On an ARM device run the following command: - $ python3 -c import lxc - + $ python3 -c import lxc ACTUAL RESULT: - $ python3 -c import lxc + $ python3 -c import lxc Traceback (most recent call last): - File string, line 1, in module - File /usr/lib/python3/dist-packages/lxc/__init__.py, line 24, in module - import _lxc + File string, line 1, in module + File /usr/lib/python3/dist-packages/lxc/__init__.py, line 24, in module + import _lxc UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python3-lxc 0.9.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu3 Architecture: amd64 Date: Mon Mar 25 15:35:25 2013 MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-01-31 (418 days ago) -- 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/1159817 Title: python module lxc failed to import on ARM with: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 0: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159817/+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 1159818] [NEW] Allow architecture armhf with template ubuntu-cloud when running on ARM
Public bug reported: Currently it is not possible to use the template ubuntu-cloud with armhf because i386 and amd64 are hard-coded. It is perfectly valid to use this template with an armhf image if the host architecture is also ARM. For example the following commands works successfully (after the modification of the template to accept armhf of course) $ lxc-create -t ubuntu-cloud -n raring-test -- -d -T https://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-armhf-root.tar.gz -r raring -a armhf Note: the URL of the tarball is specified on the command line because ubuntu-cloudimg-query doesn't find an AMI for ARM even if the tarball exists. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc-templates 0.9.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu3 Architecture: amd64 Date: Mon Mar 25 15:39:42 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-01-31 (418 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug qa-daily-testing raring -- 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/1159818 Title: Allow architecture armhf with template ubuntu-cloud when running on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159818/+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 1155652] Re: cloud-final is not executed during creation of a container from template ubuntu-cloud
** Attachment added: cloud-init.log https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+attachment/3575721/+files/cloud-init.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/1155652 Title: cloud-final is not executed during creation of a container from template ubuntu-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+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 1155652] [NEW] cloud-final is not executed during creation of a container from template ubuntu-cloud
Public bug reported: When creating a container with template ubuntu-cloud the service cloud-final is not executed resulting in a incomplete installation. TEST CASE: 1. Copy the user-data script in attachment to a local directory (you can remove the package list to go faster) 2. Create a new container from the template ubuntu-cloud with the command: $ sudo lxc-create -n raring-test -t ubuntu-cloud -- -r raring -u user-data 3. Start the container and wait until installation is done: $ sudo lxc-start -n raring-test ACTUAL RESULT: cloud-final is not executed, final-message is not displayed and boot-finished is not created on disk. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0~alpha3-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Fri Mar 15 15:58:40 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2012-01-31 (408 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug raring ** Attachment added: user-data https://bugs.launchpad.net/bugs/1155652/+attachment/3575716/+files/user-data -- 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/1155652 Title: cloud-final is not executed during creation of a container from template ubuntu-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+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 1155652] Re: cloud-final is not executed during creation of a container from template ubuntu-cloud
It could be another instance of bug 1103881. If I remove the dist- upgrade from the user-data file cloud-final is executed as expected. Here are the packages that would be upgraded with a Raring beta1 tarball: The following NEW packages will be installed: libudev1 The following packages will be upgraded: apt apt-transport-https apt-utils bsdmainutils busybox-initramfs busybox-static byobu console-setup dbus dmsetup gir1.2-gudev-1.0 grub-common grub-pc grub-pc-bin grub2-common initramfs-tools initramfs-tools-bin isc-dhcp-client isc-dhcp-common keyboard-configuration kmod libapt-inst1.5 libapt-pkg4.12 libdbus-1-3 libdevmapper1.02.1 libdrm2 libgudev-1.0-0 libicu48 libkmod2 libnewt0.52 libnih-dbus1 libnih1 libpam-modules libpam-modules-bin libpam-runtime libpam0g libpci3 libpcsclite1 module-init-tools mountall pciutils python-newt python-twisted-bin python-twisted-core python3-software-properties python3-update-manager software-properties-common ssh-import-id tzdata update-manager-core update-notifier-common upstart ureadahead whiptail -- 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/1155652 Title: cloud-final is not executed during creation of a container from template ubuntu-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+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 1103881] [NEW] cloud-final is never executed if upstart is upgraded during initialization of the image
Public bug reported: During a cloud image initialization, the service cloud-final is never executed if the cloud-config script contains an upgrade directive and upstart is part of the upgraded packages: TESTCASE: 1. Download a cloud image from http://cloud-images.ubuntu.com/raring/ with an outdated version of upstart (e.g 2013.01.23 - I saved this image, if you need it and it is not available from the mirror just ask) 2. Prepare a cloud-config script with the directives (example cloud-config script used by lp:auto-package-testing attached): apt_update: true apt_upgrade: true 3. Initialize the cloud image with this cloud-config script EXPECTED RESULT: Installation finish ACTUAL RESULT The service cloud-final is never executed and the flag boot-finished is not present. cloud-init logs of a failed installation attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cloud-init (not installed) ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Thu Jan 24 09:08:19 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: Upgraded to raring on 2012-01-31 (358 days ago) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug qa-manual-testing raring rls-r-incoming running-unity ** Attachment added: cloud-init.log https://bugs.launchpad.net/bugs/1103881/+attachment/3497974/+files/cloud-init.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
cloud-config script used by lp:auto-package-testing ** Attachment added: cloud-config.txt https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3497984/+files/cloud-config.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
** Attachment added: LP1103881.dmesg https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3498350/+files/LP1103881.dmesg -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
** Attachment added: LP1103881.syslog https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3498351/+files/LP1103881.syslog -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+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 1080685] [NEW] raring cloud images: User 'ubuntu' cannot sudo
Public bug reported:
With latest cloud images and the cloud-init script below the user
'ubuntu' cannot sudo. The user is a member of adm but not admin.
==
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
ssh_authorized_keys:
- $PUBKEY
apt_sources:
- source: deb http://archive.ubuntu.com/ubuntu $RELEASE restricted multiverse
- source: deb-src http://archive.ubuntu.com/ubuntu $RELEASE restricted
multiverse
apt_update: true
apt_upgrade: true
byobu_by_default: system
packages:
- eatmydata
- linux-image-generic
- autopkgtest
- dpkg-dev
- pbuilder
- bzr
==
Log attached
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: cloud-init (not installed)
ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
Uname: Linux 3.7.0-2-generic x86_64
ApportVersion: 2.6.2-0ubuntu3
Architecture: amd64
Date: Mon Nov 19 14:07:19 2012
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: Upgraded to raring on 2012-01-31 (292 days ago)
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug qa-manual-testing raring running-unity
** Attachment added: cloud-init.log
https://bugs.launchpad.net/bugs/1080685/+attachment/3438617/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1080685
Title:
raring cloud images: User 'ubuntu' cannot sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1080685/+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 997978] Re: KVM images lose connectivity with bridged network
** Changed in: qemu-kvm (Ubuntu Precise) Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 1017847] Re: qemu segfaults when creating an armhf container on an amd64 host
qemu-user-static was installed on the system when I have been able to reproduce this error (installed on 2012-06-06 from apt log files) I tried again this morning, and it works correctly. The main difference is that qemu-user-static has been upgraded from 1.0.50-2012.03-0ubuntu3 to 1.2.0-2012.09-0ubuntu1 on 2012-09-23 (~1 week after my last test) So probably *something* has been fixed in this new upstream version. In any case, I tried without qemu-user-static installed and I get the error chroot: failed to run command `useradd': Exec format error which is expected since the emulator is not installed. I don't think it make sense to run lxc for an architecture without the right emulator installed but it is another bug than the one I initially reported and it can be closed as 'fix released' -- 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/1017847 Title: qemu segfaults when creating an armhf container on an amd64 host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1017847/+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 1017847] Re: qemu segfaults when creating an armhf container on an amd64 host
** Changed in: qemu-linaro (Ubuntu) Status: Confirmed = Fix Released -- 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/1017847 Title: qemu segfaults when creating an armhf container on an amd64 host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1017847/+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 1053239] [NEW] cloud-init 0.7.0~bzr659-0ubuntu1 upgrade fails: Template #2 in /var/lib/dpkg/info/cloud-init.templates does not contain a 'Template:' line
Public bug reported: Upgrade to cloud-init 0.7.0~bzr659-0ubuntu1 on Quantal fails with the following error: $ sudo apt-get install cloud-init Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: cloud-init 1 upgraded, 0 newly installed, 0 to remove and 156 not upgraded. Need to get 147 kB of archives. After this operation, 8,192 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ quantal/main cloud-init all 0.7.0~bzr659-0ubuntu1 [147 kB] Fetched 147 kB in 0s (705 kB/s) Preconfiguring packages ... cloud-init template parse error: Template #2 in /tmp/cloud-init.template.236500 does not contain a 'Template:' line (Reading database ... 273708 files and directories currently installed.) Preparing to replace cloud-init 0.7.0~bzr644-0ubuntu1 (using .../cloud-init_0.7.0~bzr659-0ubuntu1_all.deb) ... Unpacking replacement cloud-init ... Processing triggers for ureadahead ... Setting up cloud-init (0.7.0~bzr659-0ubuntu1) ... Installing new version of config file /etc/init/cloud-init-nonet.conf ... Installing new version of config file /etc/cloud/cloud.cfg ... Template #2 in /var/lib/dpkg/info/cloud-init.templates does not contain a 'Template:' line dpkg: error processing cloud-init (--configure): subprocess installed post-installation script returned error exit status 255 No apport report written because MaxReports is reached already Processing triggers for ureadahead ... Errors were encountered while processing: cloud-init E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: qa-manual-testing quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1053239 Title: cloud-init 0.7.0~bzr659-0ubuntu1 upgrade fails: Template #2 in /var/lib/dpkg/info/cloud-init.templates does not contain a 'Template:' line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1053239/+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 1017847] Re: qemu segfaults when creating an armhf container on an amd64 host
The problem persists on Quantal with all updates applied: $ sudo lxc-create -n quantal-armhf -t ubuntu -- -r quantal -a armhf [...] Fetched 22.1 MB in 60s (365 kB/s) qemu: uncaught target signal 11 (Segmentation fault) - core dumped /usr/share/lxc/templates/lxc-ubuntu: line 460: 29480 Segmentation fault (core dumped) chroot $rootfs apt-get update failed to execute template 'ubuntu' aborted ** Changed in: qemu-linaro (Ubuntu) Status: Incomplete = Confirmed ** Changed in: lxc (Ubuntu) Status: Incomplete = 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/1017847 Title: qemu segfaults when creating an armhf container on an amd64 host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1017847/+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 1039196] [NEW] unregister_netdevice: waiting for lo to become free. message after shutting down an lxc container
Public bug reported: On Quantal, after I shutdown an lxc-container the following message is displayed in syslog every 10s: Aug 20 21:50:23 sark kernel: [50270.380638] unregister_netdevice: waiting for lo to become free. Usage count = 1 Aug 20 21:50:34 sark kernel: [50280.617544] unregister_netdevice: waiting for lo to become free. Usage count = 1 Aug 20 21:50:44 sark kernel: [50290.854556] unregister_netdevice: waiting for lo to become free. Usage count = 1 Aug 20 21:50:54 sark kernel: [50301.091389] unregister_netdevice: waiting for lo to become free. Usage count = 1 Usage count maybe 1 or more. Then I cannot start the container again and it completely blocks the shutdown of the host system which is waiting for lo to become free. Reboot is then forced with SysRq. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu26 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Mon Aug 20 21:46:57 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to quantal on 2012-01-31 (201 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug qa-manual-testing quantal running-unity uec-images -- 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/1039196 Title: unregister_netdevice: waiting for lo to become free. message after shutting down an lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1039196/+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 1039196] Re: unregister_netdevice: waiting for lo to become free. message after shutting down an lxc container
-- 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/1039196 Title: unregister_netdevice: waiting for lo to become free. message after shutting down an lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1039196/+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
