[Bug 1512131] Re: Apparmor complains about multiple /run/dovecot file access
** Changed in: dovecot (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1512131 Title: Apparmor complains about multiple /run/dovecot file access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+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 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
FTR, same behaviour with Serge's lxcfs "testing" branch with cgfs. -- 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/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514690/+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 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
That did not fix reboot yet. I filed bug 1514690 as it's a different root cause apparenlty. @Serge: there's nothing that should "stick around", it's a reboot after all and everything including pid 1 gets restarted. It just seems that the second boot can't create the init.scope cgroup as the "outside" host still has some state from the first 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1497420/+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 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
I'm setting this to high as this breaks autopkgtesting on armhf quite badly. ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- 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/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514690/+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 1514690] [NEW] rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
Public bug reported: Even after fixing bug 1497420 rebooting containers with systemd >= 226 (i. e. with supporting unified cgroups) does not work. Build a standard xenial container (using the ubuntu template; e. g. "adt-build-lxc ubuntu xenial"), start it: sudo lxc-start -n adt-xenial -F then log in and run "sudo reboot". It shuts down, but reboot fails with Rebooting. systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04! Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create /lxc/adt-xenial/init.scope control group: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. Freezing execution. During that time, I get the following errors: Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListChildren failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info. Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListKeys failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.h ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 10 06:30:28 2015 EcryptfsInUse: Yes SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxc.conf: lxc.lxcpath = /srv/lxc ** Affects: lxc (Ubuntu) Importance: High Status: New ** Tags: amd64 apparmor apport-bug xenial -- 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/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514690/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-lts-vivid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Hi Joseph, Happy to test upstream kernels, but this setup requires a 64-bit native arm64/aarch64 kernel, which I can't see at the link provided - only 32-bit armhf kernels. Currently we're running the kernel from the linux-generic-lts-wily package: Linux swirlix18 4.2.0-16-generic #19~14.04.1-Ubuntu SMP Thu Oct 8 15:36:19 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux If you know where we can find an appropriate mainline kernel, we can get it tested. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1344009] Re: ceilometer-common installation fails, requires manual fixing using dpkg --configure -a
[Expired for ceilometer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ceilometer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubuntu. https://bugs.launchpad.net/bugs/1344009 Title: ceilometer-common installation fails, requires manual fixing using dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1344009/+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 1088169] Re: Missing membership to groups
[Expired for ceilometer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ceilometer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubuntu. https://bugs.launchpad.net/bugs/1088169 Title: Missing membership to groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1088169/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bind9 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"
In case it wasn't clear, my patch is supposed to be for the debian/ntpdate.if-up file. Also, I think the priority of this bug should be higher, it was assigned 'low' when there was no clear problem caused by the race. Systems booting with uncorrectable clock skew can be a serious problem. -- 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/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+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 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"
** Tags added: patch -- 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/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+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 1514485] Re: [SRU] cloud-init should use "nofail" instead of "bootwait"
** Patch added: "Patch candidate for 15.10" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+attachment/4515824/+files/lp-1514485-wily-deb.diff -- 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/1514485 Title: [SRU] cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+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 1503418] Re: [SRU] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon
** Tags added: regression-release wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1503418 Title: [SRU] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1503418/+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 1514485] Re: [SRU] cloud-init should use "nofail" instead of "bootwait"
** Changed in: cloud-init (Ubuntu Wily) Assignee: (unassigned) => Ben Howard (utlemming) -- 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/1514485 Title: [SRU] cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
** Tags added: patch -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+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 1498370] Re: DHCP agent: interface unplug leads to exception
** Branch linked: lp:~hopem/neutron/kilo-lp1498370 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1498370 Title: DHCP agent: interface unplug leads to exception To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+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 1514485] Re: cloud-init should use "nofail" instead of "bootwait"
Marking as "critical" owing to Azure instance death. Because Azure instances consider ephemeral devices to be ephemeral per-boot, a stop, resized, or fabric restarted instance may not come back if the instance is presented with a new ephemeral device. Linked branch has been tested. ** Changed in: cloud-init (Ubuntu Wily) Importance: High => Critical ** Summary changed: - cloud-init should use "nofail" instead of "bootwait" + [SRU] cloud-init should use "nofail" instead of "bootwait" ** Description changed: - Snapshotted instances may fail to boot due to a change in udev in 15.10. - Starting with Ubuntu 15.10, "nobootwait" != "nofail". + SRU JUSTIFICATION + + [IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" == + "nofail." However, with Ubuntu 15.10, this is no longer the case. As a + result, snapshotted, stopped and restarted, or migrated Cloud instances + may fail to boot if the ephemeral device does not match /etc/fstab. + + [FIX] Changed the default mount option to "nofail" + + [TEST] + 1. Boot Ubuntu 15.10 on Azure + 2. Upgrade cloud-init to proposed version + 3. Confirm that "nobootwait" for the ephemeral device has been changed to "nofail" + 4. Shutdown instance + 5. Restart instance, confirm it comes up + 6. Capture restarted instance + 7. Boot captured image + 8. Confirm that capture instance came back up + + [ORIGINAL REPORT] + Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail". For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2] -- [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa [2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 -- 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/1514485 Title: [SRU] cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+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 1498370] Re: DHCP agent: interface unplug leads to exception
** Branch linked: lp:~hopem/neutron/kilo-lp1498370 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1498370 Title: DHCP agent: interface unplug leads to exception To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1498370/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu Vivid) Status: New => In Progress -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1386840] Re: [SRU] failure to start a container
** Changed in: lxc (Ubuntu Trusty) Status: Incomplete => 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/1386840 Title: [SRU] failure to start a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1386840/+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 1242074] Re: lxc-ls shows wrong status
** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Invalid -- 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/1242074 Title: lxc-ls shows wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+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 1346815] Re: lxc-clone causes duplicate MAC address and IP address
** Changed in: lxc (Ubuntu Trusty) Status: Triaged => 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/1346815 Title: lxc-clone causes duplicate MAC address and IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+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 1304936] Re: lxc-clone doesn't replace the hostname in some places
** Changed in: lxc (Ubuntu Trusty) 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/1304936 Title: lxc-clone doesn't replace the hostname in some places To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304936/+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 1354375] Re: lxc-snapshot destroys container
** Changed in: lxc (Ubuntu Trusty) 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/1354375 Title: lxc-snapshot destroys container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1354375/+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 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
** Changed in: lxc (Ubuntu Precise) Status: New => Won't Fix -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+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 1304167] Re: syntax error, trusty beta-2 cloud image
** Changed in: lxc (Ubuntu Trusty) Status: New => 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/1304167 Title: syntax error, trusty beta-2 cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304167/+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 1342960] Re: comments in common.conf must be updated
** Changed in: lxc (Ubuntu Trusty) Status: Triaged => 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/1342960 Title: comments in common.conf must be updated To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1342960/+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 1514485] Re: cloud-init should use "nofail" instead of "bootwait"
** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Wily) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Status: Confirmed => In Progress ** Branch linked: lp:~utlemming/cloud-init/lp1514485 -- 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/1514485 Title: cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+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 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-tru
** Changed in: lxc (Ubuntu Trusty) 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/1410876 Title: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-trusty-lxc-template To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1410876/+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 1506652] Update Released
The verification of the Stable Release Update for juju-core has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1506652 Title: [needs-packaging] Juju 1.24.7 is not in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+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 1510345] Update Released
The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+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 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu
This bug was fixed in the package juju-core - 1.24.7-0ubuntu1~15.04.1 --- juju-core (1.24.7-0ubuntu1~15.04.1) vivid; urgency=medium * New upstream microrelease. (Lp: #1506652) * Update dep8 tests from Xenial. -- curtis.ho...@canonical.com (Curtis C. Hovey) Fri, 16 Oct 2015 17:52:18 + ** Changed in: juju-core (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1506652 Title: [needs-packaging] Juju 1.24.7 is not in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
This bug was fixed in the package livecd-rootfs - 2.349.1 --- livecd-rootfs (2.349.1) wily; urgency=medium * cloud-images: revert to old device naming (LP: #1510345). -- Ben Howard Thu, 29 Oct 2015 11:29:01 -0500 ** Changed in: livecd-rootfs (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+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 1510565] Update Released
The verification of the Stable Release Update for juju-core has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1510565 Title: [needs-packaging] Juju 1.25.0 is not in xenial and wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1510565/+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 1510565] Re: [needs-packaging] Juju 1.25.0 is not in xenial and wily
This bug was fixed in the package juju-core - 1.25.0-0ubuntu1~15.10.1 --- juju-core (1.25.0-0ubuntu1~15.10.1) wily; urgency=medium * No change backport to 15.10 (LP: #1510565). -- Robie Basak Thu, 29 Oct 2015 11:25:46 + ** Changed in: juju-core (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1510565 Title: [needs-packaging] Juju 1.25.0 is not in xenial and wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1510565/+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 1514623] [NEW] New upstream bugfix release 1.0.8 (LXC MRE)
Public bug reported: We have released LXC 1.0.7 upstream: https://linuxcontainers.org/lxc/news This will be the eigth upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU) which bugfixes for 1.0.8 have been taken from. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxc (Ubuntu Trusty) Importance: Undecided Status: In Progress ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Trusty) Status: New => In Progress ** Changed in: lxc (Ubuntu) Status: New => 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/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+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 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
This bug was fixed in the package lxc - 1.0.7-0ubuntu0.10 --- lxc (1.0.7-0ubuntu0.10) trusty; urgency=medium * Update the /proc/self/mountinfo no-symlink verification to accomodate recursive mounts. (LP: #1509752) -- Serge Hallyn Wed, 28 Oct 2015 12:21:38 -0500 ** Changed in: lxc (Ubuntu Trusty) 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/1509752 Title: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+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 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1509752 Title: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+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 1509752] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1509752 Title: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+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 1499510] Re: Fix Typo in socket attribute name in TCPKeepAliveAdapter
Separated them based on upstream. Is that what you were looking for? ** Patch added: "python-novaclient_2.22.0-0ubuntu2.debdiff" https://bugs.launchpad.net/cloud-archive/+bug/1499510/+attachment/4515779/+files/python-novaclient_2.22.0-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1499510 Title: Fix Typo in socket attribute name in TCPKeepAliveAdapter To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1499510/+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 1466458] Re: template 'none' doesn't work with lxc-create
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => 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/1466458 Title: template 'none' doesn't work with lxc-create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1466458/+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 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1497420/+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 1510619] Re: Wily: add machine fails using kvm and lxcbr0
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => 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/1510619 Title: Wily: add machine fails using kvm and lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+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 1514558] Re: New upstream bugfix release 1.1.5 (LXC MRE)
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => 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/1514558 Title: New upstream bugfix release 1.1.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514558/+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 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
@serge Sure, it's a patch to golang runtime. I'll put this on my todo list this week. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1501651/+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 1422046] Re: cinder backup-list is always listing all tenants's bug for admin
Sounds like we're agreed that this report concerns a serious bug with security implications (insofar as any means of accidentally destroying your environment is), but is not an exploitable vulnerability, does not need a CVE assignment requested by the VMT and won't lead to any official security advisory publication. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cinderclient in Ubuntu. https://bugs.launchpad.net/bugs/1422046 Title: cinder backup-list is always listing all tenants's bug for admin To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1422046/+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 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
@arges, did you want to push this patch into our package until it hits upstream? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1501651/+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 1261045] Re: Security bugfix in lxc-sshd template: add ro to the init-script
** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Won't Fix -- 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/1261045 Title: Security bugfix in lxc-sshd template: add ro to the init-script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261045/+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 1322067] Re: 3.15.0-1.x breaks lxc-attach for unprivileged containers
** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Won't Fix -- 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/1322067 Title: 3.15.0-1.x breaks lxc-attach for unprivileged containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1322067/+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 1313796] Re: [No Network] ifupdown/bridge-utils & udev/bridge-utils race condition preventing the addition of non-pre-up ports to a bridge
** Changed in: bridge-utils (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1313796 Title: [No Network] ifupdown/bridge-utils & udev/bridge-utils race condition preventing the addition of non-pre-up ports to a bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1313796/+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 1347020] Re: systemd does not boot in a container
Fixed through trusty-backports. ** Changed in: lxc (Ubuntu Trusty) Status: Triaged => 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/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+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 1514532] [NEW] automount can appear to be both in a started and stopped state
Public bug reported: I was debugging something unrelated about automount which lead me to wanting to know if had started: $ service --status-all | grep autofs [ - ] autofs # ... other stuff snipped But I then try, $ sudo initctl status autofs autofs start/running, process 1812 I looked at the init script for autofs, $ sudo /etc/init.d/autofs status * automount is not running It claims it's not running because /var/run/autofs.pid does not exist. It looks like the following starts automount, but it doesn't create a PID file, /etc/init/autofs.conf Is this some nasty interaction between this "service" thing and the old SysV init scripts? I'm not sure what the correct way of doing these things anymore, but the above behavior seems like a bug to me. Thanks for your time! ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1514532 Title: automount can appear to be both in a started and stopped state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1514532/+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 1422046] Re: cinder backup-list is always listing all tenants's bug for admin
Indeed, I agree that there is no risk for a "malicious actor" to use this flow. However there is a confirmed risk that an openstack admin can accidentally delete backups which he should not delete (and it DID happen, sadly...), when the admin is asked to launch scripts (ospurge) used to delete resources of customers who want to remove all their data... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cinderclient in Ubuntu. https://bugs.launchpad.net/bugs/1422046 Title: cinder backup-list is always listing all tenants's bug for admin To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1422046/+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 1477198] Re: Stop doesn't work on 14.04 (start-stop-daemon --pid not supported)
This worked for me in trusty with the proposed cloud-archive repository. Before, when I restarted haproxy, I got an extra process: root@juju-machine-2-lxc-0:~# service haproxy restart * Restarting haproxy haproxy ...done. root@juju-machine-2-lxc-0:~# ps fxaw|grep haproxy 32215 ?Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid 32547 ?Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid Now it's just one as expected, replacing the one that was running before: root@juju-machine-2-lxc-0:~# ps fxaw|grep haproxy 33493 pts/3S+ 0:00 \_ grep --color=auto haproxy 33483 ?Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -D -sf 33115 root@juju-machine-2-lxc-0:~# service haproxy restart * Restarting haproxy haproxy ...done. root@juju-machine-2-lxc-0:~# ps fxaw|grep haproxy 33510 pts/3S+ 0:00 \_ grep --color=auto haproxy 33507 ?Ss 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid Using version 1.5.14-1ubuntu0.15.10.1~cloud0: root@juju-machine-2-lxc-0:~# apt-cache policy haproxy haproxy: Installed: 1.5.14-1ubuntu0.15.10.1~cloud0 Candidate: 1.5.14-1ubuntu0.15.10.1~cloud0 Version table: *** 1.5.14-1ubuntu0.15.10.1~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-proposed/liberty/main amd64 Packages 100 /var/lib/dpkg/status 1.5.14-1~cloud2 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages 1.4.24-2ubuntu0.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.4.24-2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1477198 Title: Stop doesn't work on 14.04 (start-stop-daemon --pid not supported) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1477198/+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 1514558] [NEW] New upstream bugfix release 1.1.5 (LXC MRE)
Public bug reported: We have released LXC 1.1.5 upstream: https://linuxcontainers.org/lxc/news This will be the second and probably last upstream bugfix release to hit vivid. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. This release is being uploaded to: - xenial (dev release) - wily (SRU with MRE) - vivid (SRU with MRE) - trusty (backports) We're looking forward to this consistency which should make keeping track of and fixing bugs significantly easier for us. ** Affects: lxc (Ubuntu) Importance: Undecided Status: In Progress ** Affects: lxc (Ubuntu Vivid) Importance: Undecided Status: In Progress ** Affects: lxc (Ubuntu Wily) Importance: Undecided Status: In Progress ** Changed in: lxc (Ubuntu) Status: New => In Progress ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Vivid) Status: New => In Progress ** Changed in: lxc (Ubuntu Wily) Status: New => In Progress -- 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/1514558 Title: New upstream bugfix release 1.1.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514558/+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 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)
We'll be closing this one in favor of a new LXC 1.1.5 MRE. ** Changed in: lxc (Ubuntu Vivid) Status: Fix Committed => Won't Fix -- 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/1503330 Title: New upstream bugfix release 1.1.4 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1503330/+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 1514557] [NEW] New upstream bugfix release 1.1.5 (LXC MRE)
Public bug reported: We have released LXC 1.1.5 upstream: https://linuxcontainers.org/lxc/news This will be the second and probably last upstream bugfix release to hit vivid. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. This release is being uploaded to: - xenial (dev release) - wily (SRU with MRE) - vivid (SRU with MRE) - trusty (backports) We're looking forward to this consistency which should make keeping track of and fixing bugs significantly easier for us. ** Affects: lxc (Ubuntu) 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/1514557 Title: New upstream bugfix release 1.1.5 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514557/+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 1510619] Re: Wily: add machine fails using kvm and lxcbr0
This will be fixed with 1.0.8. ** Changed in: lxc (Ubuntu) Status: Confirmed => In Progress ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- 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/1510619 Title: Wily: add machine fails using kvm and lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+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 1513698] Re: $HOME variable set incorrectly inside container
The other variable wasn't visible because you didn't export it. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- 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/1513698 Title: $HOME variable set incorrectly inside container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1513698/+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 1422046] Re: cinder backup-list is always listing all tenants's bug for admin
While I agree there is a non-negligible risk presented by this behavior, I don't see how a malicious actor could use this flaw to their advantage. As such, it doesn't seem like something for which the OpenStack Vulnerability Management Team would issue an official security advisory. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cinderclient in Ubuntu. https://bugs.launchpad.net/bugs/1422046 Title: cinder backup-list is always listing all tenants's bug for admin To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1422046/+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 1502604] Re: autopkgtests fail in LXC testbed
** Changed in: lxc (Ubuntu) Importance: Undecided => Medium -- 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/1502604 Title: autopkgtests fail in LXC testbed To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+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 1501959] Re: "System error" on chfn / su with lxc-start --share-net
Any reason you're running those commands as the container PID1 instead of starting the container and using lxc-attach to run the commands inside it? What you're doing right now is unsupported as neither chfn nor su are init processes, so they will not know how to setup the container or handled other tasks that init is in charge of (signal handling, child re-parenting and reaping, ...). ** Changed in: lxc (Ubuntu) Status: New => 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/1501959 Title: "System error" on chfn / su with lxc-start --share-net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1501959/+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 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency
Note that newer lxc-checkconfig knows to check for those modules in your kernel config so it should report what you're missing. -- 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/1508577 Title: [wily] installing juju-local on ARM64 failed. broken apt dependency To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1508577/+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 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency
Looks like you're running LXC on a system which doesn't have the needed kernel options (in this case iptables modules). This isn't a supported configuration. Closing this bug report. ** Changed in: lxc (Ubuntu) Status: Incomplete => Invalid -- 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/1508577 Title: [wily] installing juju-local on ARM64 failed. broken apt dependency To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1508577/+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
Re: [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
> restarted bind9, and again nothing:
Just to be sure - you did also retry stop+start of lxc-net after restarting
bind9, right?
--
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/1452601
Title:
vivid container's networking.service fails on boot with signal=PIPE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+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 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1507463 Title: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+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 1477453] Re: lxc-stop -n unknown-container creates a corrupted container
stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ lxc-stop -n foo ; lxc-destroy -n foo ; lxc-clone clean-machine foo foo is not running Container is not defined Error: container clean-machine is not defined ** Changed in: lxc (Ubuntu) Status: New => 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/1477453 Title: lxc-stop -n unknown-container creates a corrupted container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1477453/+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 1496877] Re: apparmor profile fails to load in Ubuntu 15.04
** Package changed: lxc (Ubuntu) => apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1496877 Title: apparmor profile fails to load in Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1496877/+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 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+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 1477130] Re: timedatectl fails inside container
Seems to work fine here: root@ubuntu:~# timedatectl Local time: Mon 2015-11-09 18:33:40 UTC Universal time: Mon 2015-11-09 18:33:40 UTC RTC time: n/a Time zone: Etc/UTC (UTC, +) Network time on: yes NTP synchronized: yes RTC in local TZ: no That's with a 15.10 container on a 14.04 host. I suspect this was actually a systemd issue where the daemon side of this wasn't starting somehow. ** Package changed: lxc (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => 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/1477130 Title: timedatectl fails inside container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1477130/+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 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
So was this bug just about you reaching the quota and LXC failing then? Just checking whether there's an actual bug we need to fix ASAP or if it's just about better error handling. ** 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/1470580 Title: unprivileged lxc containers fails with custom bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1471358] Re: lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel missing memory controller
** Changed in: lxc (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/1471358 Title: lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel missing memory controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471358/+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 1244349] Re: lxc-ubuntu-cloud should use simplestreams
*** This bug is a duplicate of bug 1182458 *** https://bugs.launchpad.net/bugs/1182458 ** This bug has been marked a duplicate of bug 1182458 ubuntu-cloud template: use simplestreams to add integrity verification -- 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/1244349 Title: lxc-ubuntu-cloud should use simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1244349/+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 529611] Re: No Upgrade Path from openvz to lxc available
Closing this, we don't have any Ubuntu release with supported VZ anymore (last was hardy). ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- 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/529611 Title: No Upgrade Path from openvz to lxc available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/529611/+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 1339781] Re: centos 7 needs setpcap capability
** 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/1339781 Title: centos 7 needs setpcap capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1339781/+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 930652] Re: lxc & swapoff: Not superuser
We're not going to fix this in LXC as the failure is obviously intended. However with lxcfs we can now render /proc/swaps in a more consistent way, including hiding swap for containers which shouldn't have any swap access. ** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- 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/930652 Title: lxc & swapoff: Not superuser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930652/+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 1367730] Re: container root directory has broken permissions with tight umask and --keep-data
root@blah-o24tmx0f:/# ls -ld / drwxr-xr-x 1 root root 18 Nov 9 18:13 / ** Changed in: lxc (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/1367730 Title: container root directory has broken permissions with tight umask and --keep-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367730/+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 1389849] Re: sudo service lxc-net restart does not reload dnsmasq when there is a container running
root@dakara:~# ps aux | grep lxc-dnsm lxc-dns+1551 0.0 0.0 28204 1096 ?SOct31 0:18 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative --dhcp-range=2607:f2c0:f00f:2760::1,ra-only --listen-address 2607:f2c0:f00f:2760::1 root 1697815 0.0 0.0 11780 940 pts/33 S+ 13:14 0:00 grep --color=auto lxc-dnsm root@dakara:~# brctl show bridge name bridge id STP enabled interfaces lxcbr0 8000.fe443b4e3bcb no veth3O4O1Q vethKVIT3V vethXEK7VF root@dakara:~# restart lxc-net lxc-net start/running root@dakara:~# ps aux | grep lxc-dnsm lxc-dns+ 1697873 0.0 0.0 28204 976 ?S13:15 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative --dhcp-range=2607:f2c0:f00f:2760::1,ra-only --listen-address 2607:f2c0:f00f:2760::1 root 1697877 0.0 0.0 11776 940 pts/33 R+ 13:15 0:00 grep --color=auto lxc-dnsm ** Changed in: lxc (Ubuntu) Status: Triaged => 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/1389849 Title: sudo service lxc-net restart does not reload dnsmasq when there is a container running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389849/+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
** Changed in: lxc (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/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 1197303] Re: lxc ubuntu-cloud template defaults to lucid when on >= raring
** Changed in: lxc (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/1197303 Title: lxc ubuntu-cloud template defaults to lucid when on >= raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1197303/+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 1424143] Re: lxc-net should attempt to use ip before ifconfig, not vice-versa
** 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/1424143 Title: lxc-net should attempt to use ip before ifconfig, not vice-versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+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 1458180] Re: Vivid/wily + wall badly broken
- What Ubuntu version are you using? - What LXC version are you using? - Is the container privileged or not? - Where did you see this behavior (over ssh to the container, in a lxc-console shell or in lxc-attach)? That should help figure out what's going on a bit more. ** Changed in: lxc (Ubuntu) Status: Triaged => Incomplete ** Changed in: lxc (Ubuntu) Importance: Medium => Undecided -- 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/1458180 Title: Vivid/wily + wall badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458180/+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 1475751] Re: need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable ppa overaly)
** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Medium => Wishlist -- 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/1475751 Title: need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable ppa overaly) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475751/+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 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24
** Changed in: lxc (Ubuntu Wily) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu Xenial) Status: Confirmed => 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/1510108 Title: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+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 1417909] Re: Container fails to start with error mounting /sys/fs/cgroup
Just re-read through this whole bug. It looks like what broke your setup is actually a bugfix in LXC wrt config inheritance. Your config contains: - lxc.mount.auto = - lxc.mount.auto = cgroup:mixed This instructs LXC (and that wasn't implemented right at first) to wipe all of lxc.mount.auto, and then set cgroup:mixed. Doing so unsets the default which did contain sys:mixed, causing the breakage you had. So the issue is that LXC actually does what you ask it to do now :) ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- 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/1417909 Title: Container fails to start with error mounting /sys/fs/cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+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 1466458] Re: template 'none' doesn't work with lxc-create
Works fine here both privileged and unprivileged, so looks like we fix this somehow in recent releases. I'll have this issue be closed with the 1.1.5 upload. ** Changed in: lxc (Ubuntu) Status: Triaged => In Progress -- 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/1466458 Title: template 'none' doesn't work with lxc-create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1466458/+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 700741] Re: dovecot won't start during boot
There was apparently a regression in Ubuntu 15.10 since I started experiencing exactly the same problem with dovecot server failing to start on system boot after upgrading my computer to release 15.10 (from 15.04): $ sudo systemctl status dovecot.service ● dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/lib/systemd/system/dovecot.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2015-11-09 12:15:21 EST; 4min 21s ago Process: 798 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89) Main PID: 798 (code=exited, status=89) Nov 09 12:15:21 dovecot[798]: master: Error: service(imap-login): listen(192.168.1.100, 143) failed: Cannot assign...address Nov 09 12:15:21 dovecot[798]: master: Error: bind(192.168.1.100, 993) failed: Cannot assign requested address Nov 09 12:15:21 dovecot[798]: master: Error: service(imap-login): listen(192.168.1.100, 993) failed: Cannot assign...address Nov 09 12:15:21 dovecot[798]: Error: service(imap-login): listen(192.168.1.100, 143) failed: Cannot assign requested address Nov 09 12:15:21 dovecot[798]: Error: bind(192.168.1.100, 993) failed: Cannot assign requested address Nov 09 12:15:21 dovecot[798]: Error: service(imap-login): listen(192.168.1.100, 993) failed: Cannot assign requested address Nov 09 12:15:21 dovecot[798]: Fatal: Failed to start listeners Nov 09 12:15:21 systemd[1]: dovecot.service: Main process exited, code=exited, status=89/n/a Nov 09 12:15:21 systemd[1]: dovecot.service: Unit entered failed state. Nov 09 12:15:21 systemd[1]: dovecot.service: Failed with result 'exit-code'. The network interface is configured dynamically by the DHCP server on the router. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/700741 Title: dovecot won't start during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/700741/+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 1384783] Re: Allow group-based entries in /etc/lxc/lxc-usernet
** 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/1384783 Title: Allow group-based entries in /etc/lxc/lxc-usernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384783/+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 1402763] Re: Multicast traffic not propating correctly over linux bridge
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1402763 Title: Multicast traffic not propating correctly over linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402763/+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 1358306] Re: lxc postinst incorrectly chooses network address to use
** Changed in: lxc (Ubuntu) Status: Confirmed => 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/1358306 Title: lxc postinst incorrectly chooses network address to use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1358306/+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 1394249] Re: lxc package dependencies over-constrained
It absolutely does depend on it as the init script will fail to start if it's not there. Note that lxc-net can be turned off by the user and dnsmasq-base doesn't install any daemon. Marking this won't fix. ** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- 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/1394249 Title: lxc package dependencies over-constrained To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1394249/+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 1240757] Re: Bridge not created if bind9 is on
Unfortunately this isn't something that LXC itself can do, unless there is some kind of .d mechanism where we can dump a bind config snippet into. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1240757 Title: Bridge not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1240757/+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 1279041] Re: /proc/sys/net/ipv4/ip_local_reserved_ports not writable because of apparmor
root@precise-gui:/# ls -lh /proc/sys/net/ipv4/ip_local_port_range -rw-r--r-- 1 nobody nogroup 0 Nov 9 12:53 /proc/sys/net/ipv4/ip_local_port_range root@precise-gui:/# uname -a Linux precise-gui 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 i686 i686 i386 GNU/Linux So looks like this got fixed at some point somehow, marking fix released. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lxc (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/1279041 Title: /proc/sys/net/ipv4/ip_local_reserved_ports not writable because of apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279041/+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 1197754] Re: print lxc-start-ephemeral container name in a machine-readable way
stgraber@dakara:~/data/code/lxc/lxc$ lxc-start-ephemeral -o blah -d | grep
"lxc-console" | awk '{print $NF}'
blah-psrfp_3s
Not the prettiest thing ever, but definitively doable with current
lxc-start-ephemeral.
I won't be spending more time on lxc-start-ephemeral though as we'll have the
new lxc-copy there soon that will take-over most if not all of it
(lxc-start-ephemeral will likely be gone in 2.0).
So marking this fix-released as the above does work.
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1197754
Title:
print lxc-start-ephemeral container name in a machine-readable way
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1197754/+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] Re: Empty log file when a container is started with the API
** Changed in: lxc (Ubuntu) Status: Confirmed => 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/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 1184936] Re: lxc-clone freezes if copied container is running [12.04 kernel 3.8]
I guess I should look at backporting 1.0.8 back to precise which should fix that. -- 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/1184936 Title: lxc-clone freezes if copied container is running [12.04 kernel 3.8] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1184936/+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 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option
Hello Peter, or anyone else affected, Accepted haproxy into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/haproxy/1.5.14-1ubuntu0.15.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: haproxy (Ubuntu Wily) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481737 Title: HAProxy init script does not work correctly with nbproc configuration option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+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
