[Bug 1400394] [NEW] Unity8 fails to start applications under systemd init (cgmanager issue?)
You have been subscribed to a public bug: Using unity8 desktop on vivid, when booting with systemd it's not possible to start applications from the unity8 dash, that could be an issue with ubuntu-app-launch/cgmanager ** Affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New -- Unity8 fails to start applications under systemd init (cgmanager issue?) https://bugs.launchpad.net/bugs/1400394 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. -- 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 1400394] Re: Unity8 fails to start applications under systemd init (cgmanager issue?)
I got u-desktop-next to boot, and confirm that starting cgmanager fixes app startup. ** Package changed: systemd (Ubuntu) = cgmanager (Ubuntu) ** Changed in: cgmanager (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1400394 Title: Unity8 fails to start applications under systemd init (cgmanager issue?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1400394/+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 1381768] Re: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1381768 Title: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1381768/+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 1403217] Re: Sync acpica-unix 20141107-1 (main) from Debian unstable (main)
This bug was fixed in the package acpica-unix - 20141107-1 Sponsored for Jackson Doak (noskcaj) --- acpica-unix (20141107-1) unstable; urgency=medium * Upgrade to latest upsteam * Refresh patches as needed. -- ahs3 a...@debian.org Mon, 17 Nov 2014 18:06:06 -0700 acpica-unix (20140926-1) unstable; urgency=medium * Upgrade to latest upstream. * Refresh patches as needed. -- ahs3 a...@debian.org Wed, 01 Oct 2014 15:30:54 -0600 acpica-unix (20140828-1) unstable; urgency=medium * Upgrade to latest upstream. * Refresh patches as needed. * Closes: #756838 -- re-enable build on big-endian systems (needed to add a patch to do so) -- Al Stone a...@debian.org Fri, 29 Aug 2014 14:42:27 -0600 acpica-unix (20140724-1) unstable; urgency=medium * Upgrade to latest upstream. * Closes: #752950 -- refreshed patches so they apply properly * Refresh some of the patches. -- Al Stone a...@debian.org Mon, 28 Jul 2014 14:47:02 -0600 acpica-unix (20140424-1) unstable; urgency=medium * Upgrade to latest upstream. -- Al Stone a...@debian.org Wed, 07 May 2014 14:30:05 -0600 acpica-unix (20140325-1) unstable; urgency=medium * Upgrade to latest upstream. * Closes: #743011 -- don't rely on uname to determine word size; just used the patch supplied in the BTS -- Al Stone a...@debian.org Mon, 07 Apr 2014 11:38:35 -0600 ** Changed in: acpica-unix (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to acpica-unix in Ubuntu. https://bugs.launchpad.net/bugs/1403217 Title: Sync acpica-unix 20141107-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpica-unix/+bug/1403217/+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 1403415] Re: apache2 crashed with SIGSEGV in zend_execute()
*** This bug is a duplicate of bug 1303170 *** https://bugs.launchpad.net/bugs/1303170 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1303170, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1403415/+attachment/4282623/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282625/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282626/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282627/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282628/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282629/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1403415/+attachment/4282630/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1303170 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1403415 Title: apache2 crashed with SIGSEGV in zend_execute() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1403415/+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
Things appear to be somewhat random; however setting the multicast_querier flag to 1 resulted in all my clustered spring back to life: for i in `seq 0 10`; do juju ssh $i echo -n 1 | sudo tee /sys/devices/virtual/net/juju-br0/bridge/multicast_querier; done Juju creates a bridge where this is not enabled by default. ** Changed in: linux (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/1402763 Title: Multicast traffic not propating correctly over linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+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 1403204] Re: Sync numactl 2.0.10-1 (main) from Debian unstable (main)
This bug was fixed in the package numactl - 2.0.10-1 Sponsored for Jackson Doak (noskcaj) --- numactl (2.0.10-1) unstable; urgency=medium * Update to 2.0.10 final * Upstream now uses autoconf/make; modify rules file to use autotools cdbs class * Update standards to 3.9.6 (no changes) * Add hppa too (Closes: #764665) -- Ian Wienand i...@debian.org Wed, 22 Oct 2014 21:45:46 +1100 numactl (2.0.10~rc2-3) unstable; urgency=medium * Turns out that kernel headers aren't generic enough to work anywhere. Return arch to i386 amd64 ia64 mips mipsel mipsn32 mipsn32el mips64 mips64el powerpc powerpcspe x32 ppc64 ppc64el arm64 sparc (Closes: #762449) -- Ian Wienand i...@debian.org Sat, 27 Sep 2014 13:53:11 +1000 numactl (2.0.10~rc2-2) unstable; urgency=medium * Change architecture to any. There is no reason this can't build everywhere. (Closes: #739725) -- Ian Wienand i...@debian.org Mon, 22 Sep 2014 09:21:33 +1000 numactl (2.0.10~rc2-1) unstable; urgency=medium * Upgrade to 2.0.10-rc2 * Remove 001_no_numa.patch; fixed upstream -- Ian Wienand i...@debian.org Tue, 09 Sep 2014 21:33:32 +1000 numactl (2.0.9-1) unstable; urgency=low * Upgrade to 2.0.9 * Upgrade standards to 3.9.5 (no change) * Add 001_no_numa.patch to avoid crash when no NUMA present (Closes: #712692) -- Ian Wienand i...@debian.org Sat, 21 Jun 2014 12:34:13 +1000 ** Changed in: numactl (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1403204 Title: Sync numactl 2.0.10-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1403204/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
I simply issued sudo reboot and this happened. So I assume then that I have a different issue from the original reporter? Should I open a separate bug and stop polluting this one? In the meantime I'll pull the requested config files. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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
For context: http://en.wikipedia.org/wiki/IGMP_snooping#IGMP_querier ** Also affects: juju-core 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/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 1402763] Re: Multicast traffic not propating correctly over linux bridge
** Changed in: linux (Ubuntu) Status: Invalid = 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/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 1370249] Re: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output)
** 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 curtin in Ubuntu. https://bugs.launchpad.net/bugs/1370249 Title: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1370249/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
/etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto juju-br0 iface juju-br0 inet dhcp bridge_ports eth0 /etc/network/interfaces.d is empty -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Yes, it appears you're having a separate issue. I'd appreciate if you open a new bug for it and we can continue there. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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
I enabled the multicast_querier using a udev rule for juju-br0; however physical host reboots are still resulting in impact lxc containers not re-joining the cluster; toggling the querier off/on again resolves the issue so I'm guessing some sort of race. ** Tags added: apparmor apport-collected ** Description changed: There's a lot of supposition in the title of this bug but its currently my best guess. In this deployment, I have a number of services running in LXC containers across multiple physical hosts; each service is clustered across three units, all on separate physical hosts, using corosync and pacemaker; when using multicast to support cluster communication, I occasionally see a container drop out of the cluster and use its isolation response (to shutdown all managed services); when using unicast I've not yet see this same problem. LXC containers are bridged to the main physical network using a linux bridge: eth0 - juju-br0 - vethXXX - | vethXXX | All MTU's are standard (1500). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.6-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 15 17:20:08 2014 ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash 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 + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 17 10:16 seq + crw-rw 1 root audio 116, 33 Dec 17 10:16 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.6 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 14.04 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: Dell Inc. PowerEdge R610 + Package: lxc 1.0.6-0ubuntu0.1 + PackageArchitecture: amd64 + PciMultimedia: + + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro + ProcEnviron: + TERM=screen-bce + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro + ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images trusty uec-images apparmor + Uname: Linux 3.13.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo video + _MarkForUpload: True + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx + dmi.bios.date: 08/18/2011 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 6.0.7 + dmi.board.name: 0F0XJ6 + dmi.board.vendor: Dell Inc. + dmi.board.version: A11 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R610 + dmi.sys.vendor: Dell Inc. -- 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 1402763] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282666/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282669/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282670/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282672/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282673/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282677/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] lxc.default.txt
apport information ** Attachment added: lxc.default.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282682/+files/lxc.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282668/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282675/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] lxc-net.default.txt
apport information ** Attachment added: lxc-net.default.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282681/+files/lxc-net.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282678/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282671/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282667/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282674/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282676/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] lxcsyslog.txt
apport information ** Attachment added: lxcsyslog.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282683/+files/lxcsyslog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1402763] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1402763/+attachment/4282679/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1370249] Re: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output)
I verified this for trusty deployment with maas 1.7.0+bzr3299-0ubuntu3~trusty1 and curtin version was 0.1.0~bzr195-0ubuntu1~14.04.1~ppa0. The steps to test this was to edit the root-tgz after uncompressing and extracting it, doing a chroot. I then did a sudo apt-get install deja- dup-backend-gvfs which also installed deja-dup and fonts-dejavu-core. The non-ascii characters were in description for deja-dup-backend-gvfs: Remote server support for Déjà Dup. After exiting, I then recreated the compressed tgz image from the modified files and copied the file to cached filename in /var/lib/maas/boot-resources/cache, and to root-tgz file in /var/lib/maas/boot- resources/current/ubuntu/amd64/generic/trusty/daily. Finally, I restarted tgt. I then deployed trusty through maas which worked. The 2nd test was to do a juju bootstrap which also passed. To make sure that I was dealing with the right image, I verified that the deja-up packages were installed on the deployed node. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1370249 Title: 'ascii' codec can't decode byte 0xc3 in position 19027: ordinal not in range(128) (curtin can't handle non-ascii characters in dpkg --list output) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1370249/+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 1384943] Re: [SRU] Pinger crashes with segfault in libc
I download 6.2 source package and recompile it on my ubuntu 14.04 trusty system but now pinger have some problems: It seems that if pinger receive a Packet too big ICMP v6 packet while is pinging an ipv6 address run into strange errors, here is what I found in the log activating debug: 2014/12/17 11:06:20.182| cc(206) SendEcho: x=40 2014/12/17 11:06:20.182| c(116) Log: pingerLog: 1418810780.182442 [2a00:1450:4002:801::1016]0 2014/12/17 11:06:20.204| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:06:20.204| c(116) Log: pingerLog: 1418810780.204457 [2a00:1450:4002:801::1016]129 Echo Reply 22ms 1 hops 2014/12/17 11:06:20.204| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:06:20.577| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:06:20.578| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': munmap_chunk(): invalid pointer: 0x7f5550efb260 *** 2014/12/17 11:17:24.223| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016] off to ICMPv6 module. 2014/12/17 11:17:24.223| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1016]. 2014/12/17 11:17:24.223| cc(206) SendEcho: x=40 2014/12/17 11:17:24.224| c(116) Log: pingerLog: 1418811444.223975 [2a00:1450:4002:801::1016]0 2014/12/17 11:17:24.246| cc(263) Recv: 40 bytes from [2a00:1450:4002:801::1016] 2014/12/17 11:17:24.246| c(116) Log: pingerLog: 1418811444.246856 [2a00:1450:4002:801::1016]129 Echo Reply 23ms 1 hops 2014/12/17 11:17:24.247| nger.cc(235) SendResult: return result to squid. len=78 2014/12/17 11:17:24.618| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:17:24.618| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': free(): invalid size: 0x7f32eb024260 *** 2014/12/17 11:19:27.987| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1015] off to ICMPv6 module. 2014/12/17 11:19:27.987| cc(194) SendEcho: Send Icmp6 packet to [2a00:1450:4002:801::1015]. 2014/12/17 11:19:27.987| cc(206) SendEcho: x=40 2014/12/17 11:19:27.987| c(116) Log: pingerLog: 1418811567.987412 [2a00:1450:4002:801::1015]0 2014/12/17 11:19:28.004| cc(263) Recv: 282 bytes from [2001:1418:100:84df:1::1] 2014/12/17 11:19:28.004| cc(306) Recv: [2001:1418:100:84df:1::1] said: 2/0 Packet Too Big *** Error in `(pinger)': double free or corruption (out): 0x7f155f608260 *** 2014/12/17 11:20:14| recv: (111) Connection refused 2014/12/17 11:20:14| Closing Pinger socket on FD 28 after every one of this error pinger exit. If I restart squid I came into the error again since my ipv6 is a tunnel and i can get a lot of this ICMP packet too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+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
Even post toggling the querier off/no, multicast is still unreliable, with cluster members failing to transmit data successfully to each other. ** Changed in: linux (Ubuntu) Status: Incomplete = 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/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 1402763] Re: Multicast traffic not propating correctly over linux bridge
Just to fill in a bit more detail, the physical hosts have multiple lxc containers (~3 each), any of which will be participating in a different multicast group; containers in the same group are spread across different physical hosts. -- 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 1402763] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/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 1396068] Re: [Xen/xl] dom0 needs to run qemu for qcow access
Upgraded a Trusty and Utopic host to the proposed version and verified that the qemu process was running in dom0 after that. ** 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 xen in Ubuntu. https://bugs.launchpad.net/bugs/1396068 Title: [Xen/xl] dom0 needs to run qemu for qcow access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1396068/+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 1394327] Re: unmapping of persistent grants in qemu
Upgraded a Trusty and Utopic host with qemu from proposed (after also upgrading xen for bug #1396068). After that defined a PV guest using a qcow2 image and booted that. No errors in dmesg and both VMs started. ** 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 qemu in Ubuntu. https://bugs.launchpad.net/bugs/1394327 Title: unmapping of persistent grants in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1394327/+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 889656] Re: installer stops using proxy
This is fixed since the python code (instead of bash) behaves properly now. Closing this bug (it's old, bug triage has taken a lot of dust). Feel free to reopen should this sting you again. ** Changed in: squid-deb-proxy (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/889656 Title: installer stops using proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/889656/+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 1166667] Re: The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
This should be fixed in the next version of squid-deb-proxy when it's released. ** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/117 Title: The default configuration is missing the /etc/squid-deb- proxy/autogenerated/pkg-blacklist-regexp.acl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117/+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 1403499] [NEW] apache2 mod_reqtimeout erroneous timeouts
Public bug reported: Please update mod_reqtimeout from Apache 2.4 upstream. There is bug 56216 (mod_reqtimeout: Resolve unexpected timeouts on keepalive requests under the Event MPM.) , see https://issues.apache.org/bugzilla/show_bug.cgi?id=56216 The fix has been committed to Apache 2.4 and will be in 2.4.11. We can reproduce the bug on Ubuntu 14.04 with package apache2 version 2.4.7-1ubuntu4. The fix can be retrieved from http://svn.apache.org/viewvc?view=revisionrevision=1587697 Thanks for considering this. Regards, Martin ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1403499 Title: apache2 mod_reqtimeout erroneous timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1403499/+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
Anything else that's special on that network, e.g. non-standard MTU? -- 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 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core Status: In Progress = Fix Committed -- 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/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1327846] Re: Samba, Ubuntu 14.04, smbpasswd, failed to open var/libsamba/private/secrets.tdb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1327846 Title: Samba,Ubuntu 14.04,smbpasswd,failed to open var/libsamba/private/secrets.tdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1327846/+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 1377325] Re: The ppc64/arm versions of Juju should depend on a more recent version of libgo5
Verified libgo5 4.9.1-0ubuntu1 was used using arm64 and ppc64el build logs. I presume a full SRU verification of the original failure case isn't needed here because this SRU is an MRE. ** 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 juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1377325 Title: The ppc64/arm versions of Juju should depend on a more recent version of libgo5 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1377325/+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 1343301] Re: juju-local needs new dep dbus -- specifically to work in lxc
Verified that dbus now correctly appears in dependencies for juju-local and juju-local-kvm in trusty-proposed. My LXC cloud image already has dbus installed, but I think it's trivial enough to consider verified. ** 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 juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1343301 Title: juju-local needs new dep dbus -- specifically to work in lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1343301/+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 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core/1.21 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/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1382842] Re: SRU breaks pacemaker in 14.04
** Changed in: hacluster (Juju Charms Collection) Assignee: (unassigned) = Edward Hope-Morley (hopem) ** Changed in: hacluster (Juju Charms Collection) Importance: Undecided = High ** Changed in: hacluster (Juju Charms Collection) Status: New = In Progress ** Branch linked: lp:~hopem/charms/trusty/hacluster/dont-allow- pacemaker-upgrade -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1382842 Title: SRU breaks pacemaker in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1382842/+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 1350947] Re: apparmor: no working rule to allow making a mount private
** Tags added: canonical-bootstack -- 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/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
This was the test case: 1) Update trusty daily root-tgz image with a copy of dcap and cap properties. 2) Sync image to cache 3) Deploy a node with trusty 4) Access deployed node 5) Ensure that cap properties for the new file are preserved on deployed system. This test passed. Here are test details: == 1) Update image root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l usr/bin/dpkgcap -rwxr-xr-x 1 root root 261840 Dec 17 09:33 usr/bin/dpkgcap root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# getcap usr/bin/dpkgcap usr/bin/dpkgcap = cap_net_raw+p root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# tar --xattrs '--xattrs-include=*' -czf root.tar.gz * tar: root.tar.gz: file changed as we read it 2) Sync image root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l total 550812 drwxr-xr-x 2 root root 4096 Dec 17 02:54 bin drwxr-xr-x 3 root root 4096 Dec 8 14:34 boot drwxr-xr-x 6 root root 4096 Dec 8 14:34 dev drwxr-xr-x 96 root root 4096 Dec 17 02:56 etc drwxr-xr-x 2 root root 4096 Apr 10 2014 home lrwxrwxrwx 1 root root33 Dec 8 14:33 initrd.img - boot/initrd.img-3.13.0-40-generic drwxr-xr-x 22 root root 4096 Dec 8 14:31 lib drwxr-xr-x 2 root root 4096 Dec 4 18:40 lib64 drwx-- 2 root root 4096 Dec 4 18:43 lost+found drwxr-xr-x 2 root root 4096 Dec 4 18:40 media drwxr-xr-x 2 root root 4096 Apr 10 2014 mnt drwxr-xr-x 2 root root 4096 Dec 4 18:40 opt drwxr-xr-x 2 root root 4096 Apr 10 2014 proc drwx-- 2 root root 4096 Dec 17 02:05 root -rw-r--r-- 1 root root 563942052 Dec 17 09:40 root.tar.gz drwxr-xr-x 4 root root 4096 Dec 8 14:33 run drwxr-xr-x 2 root root 4096 Dec 17 02:54 sbin drwxr-xr-x 2 root root 4096 Dec 4 18:40 srv drwxr-xr-x 2 root root 4096 Mar 12 2014 sys drwxrwxrwt 4 root root 4096 Dec 17 02:55 tmp drwxr-xr-x 10 root root 4096 Dec 4 18:40 usr drwxr-xr-x 12 root root 4096 Dec 4 18:43 var lrwxrwxrwx 1 root root30 Dec 8 14:33 vmlinuz - boot/vmlinuz-3.13.0-40-generic root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 -rw-r--r-- 1 root root 424884409 Dec 17 03:28 ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# cp root.tar.gz ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# ls -l ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 -rw-r--r-- 1 root root 563942052 Dec 17 09:42 ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# service tgt restart tgt stop/waiting tgt start/running, process 16692 root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# cp ../root-tgz-3d15bdc99ae5cfe7e0be2e06e084636dc6fd809ec09ca54732ec83c9224376a2 ../../current/ubuntu/amd64/generic/trusty/daily/root-tgz root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# sync;sync root@ubuntumaas:/var/lib/maas/boot-resources/cache/root# exit logout 3) Deploy node from maas 4) Access deployed node lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh 192.168.224.100 @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is 5b:1b:de:c3:ff:d6:e5:64:3c:b7:be:19:55:69:b5:7e. Please contact your system administrator. Add correct host key in /home/lmic/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/lmic/.ssh/known_hosts:20 remove with: ssh-keygen -f /home/lmic/.ssh/known_hosts -R 192.168.224.100 ECDSA host key for 192.168.224.100 has changed and you have requested strict checking. Host key verification failed. lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh-keygen -f /home/lmic/.ssh/known_hosts -R 192.168.224.100 # Host 192.168.224.100 found: line 20 type ECDSA /home/lmic/.ssh/known_hosts updated. Original contents retained as /home/lmic/.ssh/known_hosts.old lmic@ubuntumaas:/var/lib/maas/boot-resources/cache/root$ ssh 192.168.224.100 The authenticity of host '192.168.224.100 (192.168.224.100)' can't be established. ECDSA key fingerprint is 5b:1b:de:c3:ff:d6:e5:64:3c:b7:be:19:55:69:b5:7e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.224.100' (ECDSA) to the list of known hosts. Permission denied (publickey).
[Bug 1394327] Re: unmapping of persistent grants in qemu
thanks for verifying it, Stefan! -- 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/1394327 Title: unmapping of persistent grants in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1394327/+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
** Tags added: lxc network ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core 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/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
Re: [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit
@Mario, the external snapshots have apparently been around a long time. The ability to create external snapshots from running vms is newer, but it appears to exist evn in qemu-kvm 1.0. So all versions in Debian and Ubuntu should support them. http://wiki.qemu.org/Features/Snapshots#Snapshot_command_flow -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1025244 Title: qcow2 image increasing disk size above the virtual limit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1025244/+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 1403617] [NEW] gce datasource does not handle instance ssh keys
You have been subscribed to a public bug: The GCE Datasource pulls the per-project SSH but does not handle the per-instance SSH keys. The meta-data that it handles is: url_map = [ ('instance-id', 'instance/id', True), ('availability-zone', 'instance/zone', True), ('local-hostname', 'instance/hostname', True), ('public-keys', 'project/attributes/sshKeys', False), ('user-data', 'instance/attributes/user-data', False), ] It should also handle: ('public-keys', 'instance/attributes/sshKeys', False), ** Affects: cloud-init (Ubuntu) Importance: Medium Assignee: Daniel Watkins (daniel-thewatkins) Status: Confirmed -- gce datasource does not handle instance ssh keys https://bugs.launchpad.net/bugs/1403617 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. -- 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 1403617] [NEW] gce datasource does not handle instance ssh keys
Public bug reported: The GCE Datasource pulls the per-project SSH but does not handle the per-instance SSH keys. The meta-data that it handles is: url_map = [ ('instance-id', 'instance/id', True), ('availability-zone', 'instance/zone', True), ('local-hostname', 'instance/hostname', True), ('public-keys', 'project/attributes/sshKeys', False), ('user-data', 'instance/attributes/user-data', False), ] It should also handle: ('public-keys', 'instance/attributes/sshKeys', False), ** Affects: cloud-init (Ubuntu) Importance: Medium Assignee: Daniel Watkins (daniel-thewatkins) Status: Confirmed ** Package changed: ubuntu = cloud-init (Ubuntu) -- 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/1403617 Title: gce datasource does not handle instance ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1403617/+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 1366868] [seabios/trusty] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1366868 Title: kvm: dompmwakeup fails if domain becomes pmsuspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1366868/+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 1403644] [NEW] package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Previously had phpmyadmin installed through apt-get, but had purged and autocleaned. Received this error when attempting to install again. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: php5-gd 5.5.9+dfsg-1ubuntu4.5 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Dec 17 15:40:22 2014 DuplicateSignature: package:php5-gd:5.5.9+dfsg-1ubuntu4.5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-12-14 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: php5 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1403644 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1403644/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
*** This bug is a duplicate of bug 1350947 *** https://bugs.launchpad.net/bugs/1350947 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1403644] Re: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1403644 Title: package php5-gd 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1403644/+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 1403646] [NEW] /etc/init.d/autofs confuses upstart
Public bug reported: autofs 5.0.7-3ubuntu3.1 installs *both* /etc/init/autofs.conf and /etc/init.d/autofs. (One wonders what this duplication is needed for.) It is apparently possible for /etc/init.d/autofs start to be run before Upstart decides to act on /etc/init/autofs.conf. When this happens on my systems, 1) there is an automount instance running and its PID can be found in /run/autofs.pid (this is OK); 2) service autofs status prints autofs stop/waiting and returns exit code 0; 3) my Puppet configuration, which contains a service { autofs: ensure = running } or equivalent somewhere, causes noisy attempts by Upstart to restart the autofs service (which fails since the service is already running). Eventually these result in an init: autofs respawning too fast, stopped message in the logs (until the next puppet run). About point 2), I'll note that /etc/init.d/autofs status correctly prints * automount is running. However, the presence of /etc/init/autofs.conf results in the official tools (/usr/sbin/service, /usr/sbin/invoke-rc.d) ignoring /etc/init.d/autofs status. I have a hunch that the solution to this bug will be to remove /etc/init.d/autofs from the Ubuntu autofs package; is there any good reason not to do so? ** 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/1403646 Title: /etc/init.d/autofs confuses upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1403646/+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 1403648] [NEW] Apparmor denies qemu access to a number of important directories.
Public bug reported: Apparmor denise libvirt access to a number of important directories. syslog.4:Dec 12 17:18:08 nuc2 kernel: [54334.001494] type=1400 audit(1418404688.659:48): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.537222] type=1400 audit(1418404689.195:49): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.745412] type=1400 audit(1418404689.403:50): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.808978] type=1400 audit(1418404689.467:51): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.858862] type=1400 audit(1418404689.515:52): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.909608] type=1400 audit(1418404689.567:53): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 17:18:09 nuc2 kernel: [54334.976979] type=1400 audit(1418404689.635:54): apparmor=DENIED operation=open profile=libvirt-64557998-1e6b-43fb-bf6a-7dc9b9c7a660 name=/var/lib/charm/ceph/ceph.conf pid=23594 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 18:25:25 nuc2 kernel: [58368.978163] type=1400 audit(1418408725.790:56): apparmor=DENIED operation=open profile=libvirt-c2f29087-8453-4441-a27d-71fcd7a5 name=/var/lib/charm/ceph/ceph.conf pid=19293 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 18:25:25 nuc2 kernel: [58368.979670] type=1400 audit(1418408725.790:57): apparmor=DENIED operation=open profile=libvirt-c2f29087-8453-4441-a27d-71fcd7a5 name=/tmp/ pid=19293 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 syslog.4:Dec 12 18:25:25 nuc2 kernel: [58368.979680] type=1400 audit(1418408725.790:58): apparmor=DENIED operation=open profile=libvirt-c2f29087-8453-4441-a27d-71fcd7a5 name=/var/tmp/ pid=19293 comm=qemu-system-x86 requested_mask=r denied_mask=r fsuid=108 ouid=0 In this case the machine was installed using juju and maas. Specific charms in play on this machine are ceph, and nova-compute. I'm not sure if the juju charms need to be updated or if the libvirt template needs to be updated or something else altogether. It's important to not that without ceph apparmor still denies access to /tmp and /var/tmp ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1.7 ProcVersionSignature: User Name 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Dec 17 21:15:20 2014 KernLog: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.libvirt.bin: [modified] modified.conffile..etc.libvirt.libvirtd.conf: [modified] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] mtime.conffile..etc.default.libvirt.bin: 2014-12-12T02:21:56.792085 mtime.conffile..etc.libvirt.libvirtd.conf: 2014-12-12T02:21:49.403764 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: ceph (Juju Charms Collection) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images ** Also affects: ceph (Juju Charms Collection) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1403648 Title: Apparmor denies qemu access to a number of important directories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 1384931] Re: NRPE does not respect dont_blame_nrpe argument
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nagios-nrpe (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-nrpe in Ubuntu. https://bugs.launchpad.net/bugs/1384931 Title: NRPE does not respect dont_blame_nrpe argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1384931/+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 1073204] Re: ssh-authkey-fingerprints fails on boot
I am running maas-*-1.7.1 and I am still getting this on machines when trying to commission them. These machines used to commission just fine, maybe before the last update. Now nothing commissions. What kinds of logs are useful and from which machines, the maas server or the client machines that are trying to be commissioned? This is on the current 14.04.1 ubuntu. -- 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/1073204 Title: ssh-authkey-fingerprints fails on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+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 1384931] Re: NRPE does not respect dont_blame_nrpe argument
This breaks a common usage pattern for nagios-nrpe-server. People want to dynamically adjust thresholds on checks performed by the nrpe agent. On top of that, there is no security hole in the default installation. People have to explicitly enable the security hole in two configuration directives with prominent warnings. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-nrpe in Ubuntu. https://bugs.launchpad.net/bugs/1384931 Title: NRPE does not respect dont_blame_nrpe argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1384931/+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 1403681] [NEW] `service smartmontools status` broken on 10.04, smartmontools 5.38-3ubuntu3 (always replies * is not running)
Public bug reported: Package: smartmontools 5.38-3ubuntu3 Affected Ubuntu Versions: 10.04 (still in use there, supported until 4/17 as it's LTS) Defect: looks like smartmontools is never running Without the patch: $ sudo service smartmontools status * is not running Notice the missing daemon name (smartd). This is because /etc/init.d/smartmontools is passing undefined variables ($SMARTDPID, $SMARTD), to `status_of_proc` in /lsb/lsb/init-functions. With the patch: $ sudo service smartmontools status * smartd is running Fixing patch attached. I believe this has been fixed in smartmontools' 5.39 branch[1] and trunk[2] [1] http://svn.code.sf.net/p/smartmontools/code/branches/RELEASE_5_39_BRANCH/smartmontools/smartd.initd.in [2] http://svn.code.sf.net/p/smartmontools/code/trunk/smartmontools/smartd.initd.in ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New ** Patch added: patching wrong file, but really simple to apply to this package (couldn't find correct location) https://bugs.launchpad.net/bugs/1403681/+attachment/4283186/+files/smartmontools.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to smartmontools in Ubuntu. https://bugs.launchpad.net/bugs/1403681 Title: `service smartmontools status` broken on 10.04, smartmontools 5.38-3ubuntu3 (always replies * is not running) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1403681/+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 1403681] Re: `service smartmontools status` broken on 10.04, smartmontools 5.38-3ubuntu3 (always replies * is not running)
The attachment patching wrong file, but really simple to apply to this package (couldn't find correct location) seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to smartmontools in Ubuntu. https://bugs.launchpad.net/bugs/1403681 Title: `service smartmontools status` broken on 10.04, smartmontools 5.38-3ubuntu3 (always replies * is not running) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1403681/+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 378307] Re: local_scan modification and new package
Hi Andres, You wrote: the software is old and no longer maintained Not sure which software are you referring to. If you mean py-exim-localscan, is still being maintained, as you can see from its GitHub repository here: https://github.com/barryp/py-exim-localscan If you mean exim4, it is also still being maintained, as you can see from e.g. the Ubuntu changelog: http://changelogs.ubuntu.com/changelogs/pool/main/e/exim4/exim4_4.84-4ubuntu1/changelog I would also like to have py-exim-localscan as an Ubuntu package. Could you please reopen this issue, or elaborate on your reason for closing it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/378307 Title: local_scan modification and new package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/378307/+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 1403697] [NEW] package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
Public bug reported: bug ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: libapache2-mod-php5: Install libapache2-mod-php5: Configure Architecture: i386 Date: Tue Dec 16 14:51:56 2014 DuplicateSignature: package:libapache2-mod-php5:5.5.9+dfsg-1ubuntu4.5:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2012-05-16 (945 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: php5 Title: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: Upgraded to trusty on 2014-09-06 (102 days ago) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1403697 Title: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1403697/+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 1403697] Re: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1403697 Title: package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.5 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1403697/+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 1403730] [NEW] Add support for OpenVZ simfs
Public bug reported: OpenVZ simfs is currently ignored making monitoring of disk space on OpenVZ containers not possible. This has been fixed in RH: https://bugzilla.redhat.com/show_bug.cgi?id=861152 ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1403730 Title: Add support for OpenVZ simfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1403730/+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