[Bug 1447731] Re: memcache tests are skipped on python 3
i believe this was fixed in patch: https://github.com/openstack/keystonemiddleware/commit/c07ee616ae1d7e1a212dd17ba1f16a177c7acf3d also python-memcached 1.56 and newer supports py3 we can see that 312 tests are ran for py27 and for p37 tests for py27: http://logs.openstack.org/40/205440/10/check/gate-keystonemiddleware-python27/df85167/testr_results.html.gz tests for py34: http://logs.openstack.org/40/205440/10/check/gate-keystonemiddleware-python34/c713cb1/testr_results.html.gz ** Changed in: keystonemiddleware Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-keystonemiddleware in Ubuntu. https://bugs.launchpad.net/bugs/1447731 Title: memcache tests are skipped on python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/keystonemiddleware/+bug/1447731/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469299] Re: dnsmasq doesn't autostart on boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dnsmasq (Ubuntu) Status: New => Confirmed -- 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/1469299 Title: dnsmasq doesn't autostart on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1469299/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1469299] Re: dnsmasq doesn't autostart on boot
syslog: IMPOSSIBLE to start, eth0 interface unknown Nov 27 08:23:14 debussy NetworkManager[631]: WEXT support is enabled Nov 27 08:23:14 debussy dnsmasq[665]: dnsmasq: interface eth0 inconnue Nov 27 08:23:14 debussy dnsmasq[665]: interface eth0 inconnue Nov 27 08:23:14 debussy dnsmasq[665]: IMPOSSIBLE de démarrer Nov 27 08:23:14 debussy dbus[671]: [system] AppArmor D-Bus mediation is enabled -- 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/1469299 Title: dnsmasq doesn't autostart on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1469299/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1385868] Re: Samba logrotate script uses invalid argument to /etc/init.d/nmdb
seems to done the job ** 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 samba in Ubuntu. https://bugs.launchpad.net/bugs/1385868 Title: Samba logrotate script uses invalid argument to /etc/init.d/nmdb To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1385868/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Re: lxc-stop powered off a server
Hi, container config : http://paste.ubuntu.com/13524088/ /etc/apt/sources.list.d just contains a repo for some homemade backports "dpkg -l | grep lxc" was given in the initial comment, but here it is again : $ dpkg -l|grep lxc ii liblxc1 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (library) ii lxc 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools ii lxc-templates 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (templates) ii python3-lxc 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (Python 3.x bindings) I understand that "--share-net 1" can make the container connect to the host's upstart socket. I still don't think "lxc-stop" should stop the host, ever. Cheers -- 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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes
** No longer affects: haproxy (Ubuntu Trusty) -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520390] Re: package lxc 1.1.5-0ubuntu0.15.10.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
When did you last reboot this system? Also, does rebooting and then upgrading again solve it? The most likely cause for this is a network manager bug that destroys lxcbr0, this was fixed in Network Manager a few weeks back but does require you to have rebooted your system after applying those updates. ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520390 Title: package lxc 1.1.5-0ubuntu0.15.10.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520390/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup
Just upgraded to Wily here as well and I'm running into the failing autofs too. Moving from ldap client to sssd is more dramatic than desired here - how soon will the 1ubuntu3 be available in the Ubuntu Wily repos? As of the time of this post, only 5.1.1-1ubuntu2 is showing in the Wily repo. -- 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/1503034 Title: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520390] [NEW] package lxc 1.1.5-0ubuntu0.15.10.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: Just install lxc and got error. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.5-0ubuntu0.15.10.3 ProcVersionSignature: Ubuntu 4.2.0-16-generic Uname: Linux 4.2.3custombuild x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Wed Nov 18 17:44:34 2015 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2014-09-17 (435 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.2.3custombuild root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 SourcePackage: lxc SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: package lxc 1.1.5-0ubuntu0.15.10.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to wily on 2015-10-15 (42 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed wily -- 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/1520390 Title: package lxc 1.1.5-0ubuntu0.15.10.3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520390/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515463] Re: Broken juju LXC deployments
Great. Current plan is to release the SRUs on Monday, I figured releasing them over the thanksgiving weekend wouldn't be the best idea. -- 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/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515463] Re: Broken juju LXC deployments
This does indeed appear to work correctly, I've deployed a container using juju: ubuntu@apollo:~$ dpkg-query -W lxc lxc 1.0.8-0ubuntu0.3 ubuntu@apollo:~$ sudo lxc-ls --fancy NAME STATEIPV4IPV6 AUTOSTART -- juju-machine-0-lxc-0 RUNNING x.y.z.171 - YES juju-trusty-lxc-template STOPPED - - NO ubuntu@apollo:~$ sudo lxc-attach -n juju-machine-0-lxc-0 root@juju-machine-0-lxc-0:~# Thanks! -- 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/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1361940] Re: patches for cgo on arm64
** Also affects: gccgo-go (Ubuntu) Importance: Undecided Status: New ** No longer affects: gccgo-go (Ubuntu) ** No longer affects: gccgo-go (Ubuntu Utopic) ** No longer affects: gccgo-4.9 (Ubuntu Utopic) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1361940 Title: patches for cgo on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1361940/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1361946] Re: patches for cgo on arm64
Turns out these changes are required to do SRU verification for 1361940, so I've reapplied them and made a debdiff. ** Patch added: "gccgo-go_1.2.1-0ubuntu1.1_1.2.1-0ubuntu1.2.diff" https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1361946/+attachment/4526068/+files/gccgo-go_1.2.1-0ubuntu1.1_1.2.1-0ubuntu1.2.diff ** Changed in: gccgo-go (Ubuntu) Status: Invalid => In Progress ** Changed in: gccgo-go (Ubuntu Trusty) Status: New => In Progress ** Changed in: gccgo-go (Ubuntu Utopic) Status: New => Invalid ** Changed in: gccgo-go (Ubuntu) Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1361946 Title: patches for cgo on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1361946/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Re: lxc-stop powered off a server
Because it's needed for things like the Android container on Ubuntu Touch, application containers on OpenWRT, ... There are legitimate use cases for those features, those use cases just never apply when running a full Linux distro inside the container :) LXC used to default to sharing the netns by default when no lxc.network entry was set, that was clearly bad design and we've fixed that (no defaulting to an empty netns), but if someone specifically sets lxc.network.type=none or passes --share-net 1, we give them exactly what they requested. -- 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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Re: lxc-stop powered off a server
Serge, why do we offer people something which is such a landmine? -- 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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1510619 Title: Wily: add machine fails using kvm and lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515463] Re: Broken juju LXC deployments
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1504496 Title: package lxc 1.1.4-0ubuntu0.1 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/lxc/+bug/1504496/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1503330 Title: New upstream bugfix release 1.1.4 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1503330/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Re: lxc-stop powered off a server
I can't quite reproduce this information. Could you show the container configuration? Note that your host being trusty (and presumably upstart-based), if your container also is running upstart, then if you use --share-net 1, then the abstract unix socket which upstart uses to ask init to shut down will be talking in the host's network, to the host's upstart. --share-net 1 is not recommended. It is similar to 'lxc.network.type = none', of which lxc.container.conf(5) warns: none: will cause the container to share the host's network namespace. This means the host network devices are usable in the container. It also means that if both the container and host have upstart as init, 'halt' in a container (for instance) will shut down the host. -- 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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Re: lxc-stop powered off a server
Please also show the output of ls /etc/apt/sources.list.d dpkg -l | grep lxc ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
This bug was fixed in the package openssh - 1:6.9p1-3 --- openssh (1:6.9p1-3) unstable; urgency=medium * ssh_config(5): Fix markup errors in description of GSSAPITrustDns (closes: #799271). * Fix dh_install and dh_fixperms overrides to work properly with an architecture-independent-only build (closes: #806090). * Do much less work in architecture-independent-only builds. * Drop ConsoleKit session registration patch; it was only ever enabled for Ubuntu, which no longer needs it (LP: #1334916, #1502045). -- Colin Watson Tue, 24 Nov 2015 22:48:53 + ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- 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/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1502045] Re: Move from consolekit to logind
This bug was fixed in the package openssh - 1:6.9p1-3 --- openssh (1:6.9p1-3) unstable; urgency=medium * ssh_config(5): Fix markup errors in description of GSSAPITrustDns (closes: #799271). * Fix dh_install and dh_fixperms overrides to work properly with an architecture-independent-only build (closes: #806090). * Do much less work in architecture-independent-only builds. * Drop ConsoleKit session registration patch; it was only ever enabled for Ubuntu, which no longer needs it (LP: #1334916, #1502045). -- Colin Watson Tue, 24 Nov 2015 22:48:53 + ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1502045 Title: Move from consolekit to logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1502045/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525787/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525786/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxc-net.default.txt
apport information ** Attachment added: "lxc-net.default.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525788/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525785/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxc.default.txt
apport information ** Attachment added: "lxc.default.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525789/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxcsyslog.txt
apport information ** Attachment added: "lxcsyslog.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525790/+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/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] [NEW] lxc-stop powered off a server
Public bug reported: Hi, Earlier today, a server got powered off and I'm 99% sure it's because I ran the following command as root : # lxc-stop -n The container was started manually with : # lxc-start -n -F --share-net 1 and it wasn't fully booted (ie I didn't have the console yet). syslog just showed : Nov 26 11:13:12 foo kernel: [30192021.012313] init: tty4 main process (1298) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013083] init: tty5 main process (1301) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013750] init: jujud-unit-landscape-client-0 main process (1303) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.014412] init: jujud-unit-ksplice-0 main process (1306) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.015017] init: tty2 main process (1307) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.015592] init: tty3 main process (1309) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016160] init: tty6 main process (1312) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016810] init: jujud-machine-0 main process (1313) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.017423] init: jujud-unit-ubuntu-basenode-0 main process (1314) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.018583] init: tty1 main process (1784) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.019164] init: ttyS1 main process (1791) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.019738] init: cron main process (20196) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.020328] init: irqbalance main process (26014) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.020926] init: cgmanager main process (27367) killed by TERM signal and that's it. I don't have other relevant logs to offer I'm afraid. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty ~$ dpkg -l|grep lxc ii liblxc1 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (library) ii lxc 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools ii lxc-templates 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (Python 3.x bindings) apport information below Thanks --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.10 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=17a1fdea-b0d0-4f6f-a664-ec532f379c64 ro console=tty0 console=ttyS1,38400 nosplash ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Tags: trusty third-party-packages apparmor Uname: Linux 3.13.0-68-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _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 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-collected third-party-packages trusty ** Tags added: apparmor apport-collected third-party-packages trusty ** Description changed: Hi, Earlier today, a server got powered off and I'm 99% sure it's because I ran the following command as root : # lxc-stop -n The container was started manually with : # lxc-start -n -F --share-net 1 and it wasn't fully booted (ie I didn't have the console yet). syslog just showed : Nov 26 11:13:12 foo kernel: [30192021.012313] init: tty4 main process (1298) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013083] init: tty5 main process (1301) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013750] init: jujud-unit-landscape-client-0 main process (1303) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.014412] init: jujud-unit-ksplice-0 main process (1306) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.015017] init: tty2 main process (1307) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.015592] init: tty3 main process (1309) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016160] init: tty6 main process (1312) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016810] init: jujud-machine-0 main process (1313) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.01
[Bug 1520192] Re: Precise multipath-tools from precise should have been fixed together with Trusty fixes
** Description changed: - Somehow precise multipath-tools from precise was NOT fixed with fixes - added into trusty. Since SRU is based on FIXING things (and not - implementing new features) and both have the same major version, and all - changes in between them ARE FIXES, I really would like those fixes to be - SRU'ed into Precise as well: + Precise multipath-tools MIGHT need fixes from trusty. This has already + been proved in one iSCSI multipath installation where precise multipath, + intermittently, connected to VNX storages show paths as: active/failed + when it should show - even after the path check timeout - failed. - LP: #1468897 - https://bugs.launchpad.net/bugs/1468897 - LP: #1386637 - https://bugs.launchpad.net/bugs/1386637 + * Improve description showing output * - - 0001-multipath-add-checker_timeout-default-config-option.patch - - 0002-Make-params-variable-local.patch - - 0003-libmultipath-Fix-possible-string-overflow.patch - - 0004-Update-hwtable-factorization.patch - - 0005-Fixup-strip-trailing-whitespaces-for-getuid-return-v.patch - - 0006-Remove-sysfs_attr-cache.patch - - 0007-Move-setup_thread_attr-to-uevent.c.patch - - 0008-Use-lists-for-uevent-processing.patch - - 0009-Start-uevent-service-handler-from-main-thread.patch - - 0010-libmultipath-rework-sysfs-handling.patch - - 0011-Rework-sysfs-device-handling-in-multipathd.patch - - 0012-Only-check-offline-status-for-SCSI-devices.patch - - 0013-Check-for-offline-path-in-get_prio.patch - - 0014-libmultipath-Remove-duplicate-calls-to-path_offline.patch - - 0015-Update-dev_loss_tmo-for-no_path_retry.patch - - 0016-Reload-map-for-device-read-only-setting-changes.patch - - 0017-multipath-get-right-sysfs-value-for-checker_timeout.patch - - 0018-multipath-handle-offlined-paths.patch - - 0019-multipath-fix-scsi-timeout-code.patch - - 0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch - - 0021-multipath-cleanup-dev_loss_tmo-issues.patch - - 0022-Fix-for-setting-0-to-fast_io_fail.patch - - 0023-Fix-fast_io_fail-capping.patch - - 0024-multipath-enable-getting-uevents-through-libudev.patch - - 0025-Use-devpath-as-argument-for-sysfs-functions.patch - - 0026-multipathd-remove-references-to-sysfs_device.patch - - 0027-multipathd-use-struct-path-as-argument-for-event-pro.patch - - 0028-Add-global-udev-reference-pointer-to-config.patch - - 0029-Use-udev-enumeration-during-discovery.patch - - 0030-use-struct-udev_device-during-discovery.patch - - 0031-More-debugging-output-when-synchronizing-path-states.patch - - 0032-Use-struct-udev_device-instead-of-sysdev.patch - - 0033-discovery-Fixup-cciss-discovery.patch - - 0035-Use-udev-devices-during-discovery.patch - - 0036-Remove-all-references-to-hand-craftes-sysfs-code.patch - - 0037-multipath-libudev-cleanup-and-bugfixes.patch - - 0038-multipath-check-if-a-device-belongs-to-multipath.patch - - 0039-multipath-and-wwids_file-multipath.conf-option.patch - - 0040-multipath-Check-blacklists-as-soon-as-possible.patch - - 0041-add-wwids-file-cleanup-options.patch - - 0042-add-find_multipaths-option.patch + Using trusty multipath in Precise, the same environment does NOT suffer + from this issue. + + Differences between both versions: + + LP: #1468897 - https://bugs.launchpad.net/bugs/1468897 + LP: #1386637 - https://bugs.launchpad.net/bugs/1386637 + + - 0001-multipath-add-checker_timeout-default-config-option.patch + - 0002-Make-params-variable-local.patch + - 0003-libmultipath-Fix-possible-string-overflow.patch + - 0004-Update-hwtable-factorization.patch + - 0005-Fixup-strip-trailing-whitespaces-for-getuid-return-v.patch + - 0006-Remove-sysfs_attr-cache.patch + - 0007-Move-setup_thread_attr-to-uevent.c.patch + - 0008-Use-lists-for-uevent-processing.patch + - 0009-Start-uevent-service-handler-from-main-thread.patch + - 0010-libmultipath-rework-sysfs-handling.patch + - 0011-Rework-sysfs-device-handling-in-multipathd.patch + - 0012-Only-check-offline-status-for-SCSI-devices.patch + - 0013-Check-for-offline-path-in-get_prio.patch + - 0014-libmultipath-Remove-duplicate-calls-to-path_offline.patch + - 0015-Update-dev_loss_tmo-for-no_path_retry.patch + - 0016-Reload-map-for-device-read-only-setting-changes.patch + - 0017-multipath-get-right-sysfs-value-for-checker_timeout.patch + - 0018-multipath-handle-offlined-paths.patch + - 0019-multipath-fix-scsi-timeout-code.patch + - 0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch + - 0021-multipath-cleanup-dev_loss_tmo-issues.patch + - 0022-Fix-for-setting-0-to-fast_io_fail.patch + - 0023-Fix-fast_io_fail-capping.patch + - 0024-multipath-enable-getting-uevents-through-libudev.patch + - 0025-Use-devpath-as-argument-for-sysfs-functions.patch + - 0026-multipathd-remove-references-to-sysfs_device.patch + - 0027-multipathd-use-struct-path-as-argument-for-event-pro.patch + - 0028-Add-global-udev-reference-pointer-to-config.patch + - 0029-Use-udev-enumeration-during-discovery.patch + - 0
[Bug 1446906] Re: lxc container with postfix, permission denied on mailq
Please try the test kernels at http://people.canonical.com/~jj/lp1446906/ -- 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/1446906 Title: lxc container with postfix, permission denied on mailq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520192] [NEW] Precise multipath-tools from precise should have been fixed together with Trusty fixes
Public bug reported: Somehow precise multipath-tools from precise was NOT fixed with fixes added into trusty. Since SRU is based on FIXING things (and not implementing new features) and both have the same major version, and all changes in between them ARE FIXES, I really would like those fixes to be SRU'ed into Precise as well: LP: #1468897 - https://bugs.launchpad.net/bugs/1468897 LP: #1386637 - https://bugs.launchpad.net/bugs/1386637 - 0001-multipath-add-checker_timeout-default-config-option.patch - 0002-Make-params-variable-local.patch - 0003-libmultipath-Fix-possible-string-overflow.patch - 0004-Update-hwtable-factorization.patch - 0005-Fixup-strip-trailing-whitespaces-for-getuid-return-v.patch - 0006-Remove-sysfs_attr-cache.patch - 0007-Move-setup_thread_attr-to-uevent.c.patch - 0008-Use-lists-for-uevent-processing.patch - 0009-Start-uevent-service-handler-from-main-thread.patch - 0010-libmultipath-rework-sysfs-handling.patch - 0011-Rework-sysfs-device-handling-in-multipathd.patch - 0012-Only-check-offline-status-for-SCSI-devices.patch - 0013-Check-for-offline-path-in-get_prio.patch - 0014-libmultipath-Remove-duplicate-calls-to-path_offline.patch - 0015-Update-dev_loss_tmo-for-no_path_retry.patch - 0016-Reload-map-for-device-read-only-setting-changes.patch - 0017-multipath-get-right-sysfs-value-for-checker_timeout.patch - 0018-multipath-handle-offlined-paths.patch - 0019-multipath-fix-scsi-timeout-code.patch - 0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch - 0021-multipath-cleanup-dev_loss_tmo-issues.patch - 0022-Fix-for-setting-0-to-fast_io_fail.patch - 0023-Fix-fast_io_fail-capping.patch - 0024-multipath-enable-getting-uevents-through-libudev.patch - 0025-Use-devpath-as-argument-for-sysfs-functions.patch - 0026-multipathd-remove-references-to-sysfs_device.patch - 0027-multipathd-use-struct-path-as-argument-for-event-pro.patch - 0028-Add-global-udev-reference-pointer-to-config.patch - 0029-Use-udev-enumeration-during-discovery.patch - 0030-use-struct-udev_device-during-discovery.patch - 0031-More-debugging-output-when-synchronizing-path-states.patch - 0032-Use-struct-udev_device-instead-of-sysdev.patch - 0033-discovery-Fixup-cciss-discovery.patch - 0035-Use-udev-devices-during-discovery.patch - 0036-Remove-all-references-to-hand-craftes-sysfs-code.patch - 0037-multipath-libudev-cleanup-and-bugfixes.patch - 0038-multipath-check-if-a-device-belongs-to-multipath.patch - 0039-multipath-and-wwids_file-multipath.conf-option.patch - 0040-multipath-Check-blacklists-as-soon-as-possible.patch - 0041-add-wwids-file-cleanup-options.patch - 0042-add-find_multipaths-option.patch LP: #1431650 - https://bugs.launchpad.net/bugs/1431650 - Added debian/patches/0015-shared-lock-for-udev.patch LP: #1441930 - https://bugs.launchpad.net/bugs/1441930 - Support disks with non 512-byte sectors LP: #1435706 - https://bugs.launchpad.net/bugs/1435706 ( GOOD CANDIDATE ) - Correctly write FC timeout attributes to sysfs. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: In Progress ** Changed in: multipath-tools (Ubuntu) Status: New => In Progress ** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (inaddy) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1520192 Title: Precise multipath-tools from precise should have been fixed together with Trusty fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1470056] Re: openstack-dashboard-ubuntu-theme dpkg error on Ubuntu 15.04
http://paste.openstack.org/show/480091/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1470056 Title: openstack-dashboard-ubuntu-theme dpkg error on Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1470056/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs