[Bug 1514400] Re: Update to 1.0.1

** Changed in: gdisk (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1514400 Title: Update to 1.0.1 To manage notifications about this bug go

[Bug 1287111] Re: package amavisd-new-postfix 1:2.7.1-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: amavisd-new (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1287111 Title: package amavisd-new-postfix

[Bug 1422046] Re: cinder backup-list is always listing all tenants's bug for admin

It looks like bug 1514396 has been opened for the same issue in the V1 API. -- 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

[Bug 1477198] Re: Stop doesn't work on 14.04 (start-stop-daemon --pid not supported)

Related bug 1481737 I think we'll try nail both of these in a single SRU for wily, and follow up on the original trusty sru for multi-proc configurations -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu.

[Bug 1514431] [NEW] vsftpd does not support non-ASCII (UTF8) characters

Public bug reported: vsftpd does not support UTF-8 character on certain versions of Ubuntu/Debian: On Ubuntu 14.04 the response to the FEAT command contains UTF8. On Ubuntu 15.04, 15.10 and Debian 8 the response to the FEAT command does not contain UTF8 and the status message is: 'Status:

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

** Also affects: haproxy (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: haproxy (Ubuntu Xenial) Importance: Medium Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

Please can we ensure that this is actually fixed in the current development release as well; we're backporting haproxy to 14.04 as part of the Ubuntu Cloud Archive, so having backwards compat in the latest packages with 14.04 is important. -- You received this bug notification because you are a

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

Related bug 1477198 -- 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

[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 Thanks for your help. Unfortunately, I didn't have any luck with this either. I added listen-on { ! 10.0.3.1; }; just before the final "}" line. restarted bind9, and I have the same error

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

There's a small niggle in the proposed change for trusty; the 'clean' exit handling will override the exit code from the init script, resulting in the return code being 0 all of the time; dropping the exit from within 'clean' will resolve this. I've uploaded Louis' fix with this small improvement

[Bug 1285197] Re: growpart failed in ppc64el guest

FWIW, this is fixed upstream (in GPT fdisk 1.0.1), and bug 1514400 now requests an update to that version. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1285197 Title: growpart

[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

[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

[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

[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

[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

[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.

[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

[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

[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.

[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.

[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.

[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.

[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

[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

[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

[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

[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

[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,

[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

[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

[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

[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

[Bug 1514482] [NEW] walinuxagent udev should be included in initramfs

You have been subscribed to a public bug: The Azure resource disk udev rule should be included in the initramfs. ** Affects: walinuxagent (Ubuntu) Importance: High Assignee: Ben Howard (utlemming) Status: Confirmed -- walinuxagent udev should be included in initramfs

[Bug 1514485] Re: cloud-init should use "nofail" instead of "bootwait"

It seems like the right thing to do is write 'nobootwait' or 'nofail' based on distro.uses_systemd() ** Description changed: 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

[Bug 1389244] Re: lxc-info output different in terminal and file redirection

Pretty sure we fixed that one a while back (and a similar issue in lxc- autostart too). ** 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.

[Bug 1449099] Re: [SRU] bcache-tools to trusty

Now that this is in trusty we also need this in Precise. Without this MAAS will not be able to deploy Precise at all, because of curtin needing bcache-tools. ** Changed in: bcache-tools (Ubuntu Trusty) Status: Triaged => Fix Released ** Summary changed: - [SRU] bcache-tools to trusty +

[Bug 1468611] Re: dnsmasq fails to start in lxc-net

** 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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1468611 Title: dnsmasq fails to start in lxc-net To manage

[Bug 1452451] Re: lxc-attach needs to mount a /proc for apparmor's use

** 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/1452451 Title: lxc-attach needs to mount a /proc for apparmor's use

[Bug 1458173] Re: Vivid + LXC autostart not working

** 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/1458173 Title: Vivid + LXC autostart not working To manage

[Bug 1449099] Re: [SRU] bcache-tools to trusty and precise

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcache-tools (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu.

[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

[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

[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,

[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

[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

[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

[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

[Bug 1414771] Re: Can not clone lxc container with lvm backingstore after ubuntu update

** 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/1414771 Title: Can not clone lxc container with lvm backingstore

[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid

** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** 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.

[Bug 1449099] Re: [SRU] bcache-tools to trusty and precise

** Also affects: bcache-tools (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1449099 Title: [SRU] bcache-tools to

[Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules

** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: lxc (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of

[Bug 1511993] Re: when trying to install the lxd package, lxc fails to install

Looks like the iptables modules aren't present or couldn't be loaded. If so, failing to start lxc-net is the right outcome. Can you tell us what kernel version you're running and what "sudo modprobe iptable_nat" says on your system? ** Changed in: lxc (Ubuntu) Status: New => Incomplete

[Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

** 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

[Bug 1261338] Re: lxc-stop and even lxc-stop -k can hang

Not seeing anything obviously wrong here... To rule out a few more things, when you get the hanging "lxc-stop -n container -k", can you do and paste the output of: - ps faux - dmesg Thanks! ** Changed in: lxc (Ubuntu) Status: Confirmed => Incomplete ** Changed in: lxc (Ubuntu)

[Bug 1303756] Re: make lxc-console work non-confusingly by default on touch images

** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu) Importance: High => 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/1303756 Title:

[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.

[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

[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

[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

[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.

[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 --

[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

[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

[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

[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 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

[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

[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.

[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:

[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

[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

[Bug 1409425] Re: lxc-start-ephemeral stops working with kernel 3.18 - overlayfs change?

** 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/1409425 Title: lxc-start-ephemeral stops working with kernel

[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.

[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

[Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

** 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup)

[Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This may be related to the lxc-net ordering issue somehow. 1.1.5 does contain a change in that unit so I'll tentatively mark it as fixed by that upload, let me know if this happens again and we'll dig deeper. ** Changed in: lxc (Ubuntu) Status: Incomplete => In Progress -- You received

[Bug 1477198] Re: Stop doesn't work on 14.04 (start-stop-daemon --pid not supported)

Hello Jorge, 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

[Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Won't Fix ** No longer affects: lxc (Ubuntu Precise) ** No longer affects: lxc (Ubuntu Saucy) ** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged

[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

[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

[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

[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

[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

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; }; >

[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

[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:

[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.

[Bug 1514485] [NEW] cloud-init should use "nofail" instead of "bootwait"

You have been subscribed to a public bug: Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail". ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- cloud-init should use "nofail" instead of

Re: [Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

Hi Martin, thanks for that info. During a reboot, lxc deletes the container's cgroup, then recreates it. Is systemd expecting the cgroup it previously created to stick around? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

** Changed in: haproxy (Ubuntu Wily) Status: New => In Progress ** Changed in: haproxy (Ubuntu Xenial) Assignee: (unassigned) => James Page (james-page) ** Changed in: haproxy (Ubuntu Wily) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification

[Bug 1514482] [NEW] walinuxagent udev should be included in initramfs

Public bug reported: The Azure resource disk udev rule should be included in the initramfs. ** Affects: walinuxagent (Ubuntu) Importance: High Assignee: Ben Howard (utlemming) Status: Confirmed ** Affects: walinuxagent (Ubuntu Wily) Importance: Undecided Status:

[Bug 1477198] Re: Stop doesn't work on 14.04 (start-stop-daemon --pid not supported)

** Changed in: haproxy (Ubuntu Xenial) Status: In Progress => Fix Released -- 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

[Bug 1514485] [NEW] cloud-init should use "nofail" instead of "bootwait"

Public bug reported: Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail". ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Wily) Importance: Undecided

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

This bug was fixed in the package haproxy - 1.6.2-2ubuntu3 --- haproxy (1.6.2-2ubuntu3) xenial; urgency=medium * d/haproxy.init: Ensure that cleanup does not override exit status of init script. -- James Page Mon, 09 Nov 2015 14:35:15 + **

[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 I have now added listen-on-v6 { none; }; restarted bind9, and again nothing: kevin@awabi:~/src$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3 -Flxc-start: conf.c:

[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:

[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:

[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

[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

  1   2   >