[Bug 1527105] [NEW] Performance: drop HANDLE_BLOCK_INTERRUPTIONS support
Public bug reported: Dropping HANDLE_BLOCK_INTERRUPTIONS, which is only used by Apache 1, and is dropped in PHP7, leads to a 4-6% speedup on artificial benchmarks and a measurable speedup on real world applications. I have written a patch to do this and submitted it upstream: https://github.com/php/php-src/pull/1532 The PHP folk are a little hesitant to merge it in case there's anyone downstream who has a custom server API that still uses the hooks. Ubuntu doesn't ship Apache 1, nor does it have any custom server APIs, so it's safe to be merged, giving all your users a speed boost. All the details and the patch are in the upstream submission, and I'm happy to answer any other questions or get it into whatever format is most useful for you. ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- 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/1527105 Title: Performance: drop HANDLE_BLOCK_INTERRUPTIONS support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1527105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] [NEW] ssh-keygen ignores $HOME
Public bug reported: The manual for ssh-keygen claims that by default it will create a key in ~/.ssh/id_rsa The convention used in /bin/sh (and other shells) is that ~/.ssh/id_rsa is basically "$HOME/.ssh/id_rsa". So changing $HOME should change where ssh-keygen writes its key. But it does not. ssh-keygen seems to use the directory extracted from /etc/passwd. In this terminal session, I change the value of $HOME to illustrate this: $ HOME=/tmp sh $ cd ~ $ pwd /tmp $ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/home/drj/.ssh/id_rsa): ^C Versions etc: $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:6.7p1-5ubuntu1.3 Candidate: 1:6.7p1-5ubuntu1.3 Version table: *** 1:6.7p1-5ubuntu1.3 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.7p1-5ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] Re: ssh-keygen ignores $HOME
Thanks! I've learnt another dpkg option now. :) -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
Bug still persists. http://askubuntu.com/questions/615129/systemd-mysql-wont-stop provides one solution + this is ugly. Normal mysql should correctly stop itself, without hacking an etc systemd service override. -- 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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1375821] Re: ifupdown doesn't bring loopback to state up
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1375821 Title: ifupdown doesn't bring loopback to state up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511735] Re: libnl: fail to bind() netlink sockets
** Also affects: libnl3 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808213 Importance: Unknown Status: Unknown -- 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/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511735] Re: libnl: fail to bind() netlink sockets
The bug report on debian has been created: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=808213 ** Bug watch added: Debian Bug tracker #808213 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808213 -- 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/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1526984] [NEW] ISST-LTE: root mpath device unavailable after installation
You have been subscribed to a public bug: Canonical FYI: We appear to have a regression in the current 14.04 environment back to the behavior originally outlined in Comment #10 of LP Bug 1429327. ---Problem--- A multipath install of 14.04.04 fails to create the install mpath device on subsequent boots. While the root filesystem ends up being mounted on top of one of the path devices, other partitions on that multipath device will not be automatically found. ---Additional details--- For one example host, the install disk was set up with a root and swap partition: Dec 14 21:37:55 disk-detect: create: mpath0 (35000c5007655a10f) undef IBM ,ST300MP0064 Dec 14 21:37:55 disk-detect: size=279G features='0' hwhandler='0' wp=undef Dec 14 21:37:55 disk-detect: |-+- policy='round-robin 0' prio=1 status=undef Dec 14 21:37:55 disk-detect: | `- 0:0:7:0 sdc 8:32 undef ready running Dec 14 21:37:55 disk-detect: `-+- policy='round-robin 0' prio=1 status=undef Dec 14 21:37:55 disk-detect: `- 1:0:3:0 sdd 8:48 undef ready running The resulting fstab entries after install were: /dev/mapper/mpath0-part2 / ext4errors=remount-ro 0 1 /dev/mapper/mpath0-part3 noneswapsw0 0 In post-install boots, the multipath command appears to be executed prior to any disks being discovered: Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... [0.612955] ipr: IBM Power RAID SCSI Device Driver version: 2.6.1 (March 12, 2015) [0.612985] ipr :80:00.0: Found IOA with IRQ: 0 [0.613478] ipr :80:00.0: ibm,query-pe-dma-windows(53) 80 800 2164 returned 0 Begin: Running /scripts/local-top ... [0.613727] ipr :80:00.0: ibm,create-pe-dma-window(54) 80 800 2164 10 21 returned 0 (liobn = 0x7164 starting addr = 800 0) Begin: Loading multipath modules ... [0.618790] device-mapper: multipath: version 1.9.0 loaded Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Waiting for scsi storage ... done. Begin: Discovering multipaths ... [0.623429] be2net 0002:01:00.0: be2net version is 10.6.0.2 [0.623587] be2net 0002:01:00.0: enabling device ( -> 0002) done. [0.636785] ipr :80:00.0: Using 64-bit direct DMA at offset 800 [0.637343] be2net 0002:01:00.0: PCIe error reporting enabled [0.641435] ipr :80:00.0: Received IRQ : 20 [0.641522] ipr :80:00.0: Request for 2 MSIXs succeeded. [0.645713] ipr :80:00.0: Starting IOA initialization sequence. [0.645719] scsi host0: IBM 0 Storage Adapter [0.645741] ipr :80:00.0: Starting IOA initialization sequence. [0.645833] ipr 0001:a0:00.0: Found IOA with IRQ: 0 [0.646221] ipr :80:00.0: Adapter firmware version: 13510C00 [0.647673] ipr :80:00.0: IOA initialized. [0.648009] ipr 0001:a0:00.0: Received IRQ : 448 [0.648041] ipr 0001:a0:00.0: Request for 2 MSIXs succeeded. [0.651764] ipr 0001:a0:00.0: Starting IOA initialization sequence. [0.651769] scsi host1: IBM 0 Storage Adapter [0.651795] ipr 0001:a0:00.0: Starting IOA initialization sequence. [0.652262] ipr 0001:a0:00.0: Adapter firmware version: 13510C00 [0.653702] ipr 0001:a0:00.0: IOA initialized. [0.660800] scsi 0:3:0:0: No Device IBM 57B1001SISIOA0150 PQ: 0 ANSI: 0 [0.660811] scsi 0:3:0:0: Resource path: 0/FE [0.672518] scsi 0:0:0:0: Direct-Access IBM ST300MP0064 7D0E PQ: 0 ANSI: 6 [0.672530] scsi 0:0:0:0: Resource path: 0/00-0E-08 ... (first device in mpath0 seen at this point): [0.710988] scsi 1:0:3:0: Direct-Access IBM ST300MP0064 7D0E PQ : 0 ANSI: 6 [0.710994] scsi 1:0:3:0: Resource path: 1/00-0E-0A The system ends up mounting the root filesystem from /dev/sdc2, and the post-mount run of multipath errors out creating mpath0: [ 10.056286] device-mapper: table: 252:0: multipath: error getting device [ 10.082644] device-mapper: table: 252:0: multipath: error getting device [ 10.192614] device-mapper: table: 252:2: multipath: error getting device [ 10.222609] device-mapper: table: 252:2: multipath: error getting device [ 10.663458] device-mapper: table: 252:2: multipath: error getting device [ 10.682690] device-mapper: table: 252:2: multipath: error getting device [ 10.796743] device-mapper: table: 252:2: multipath: error getting device Since no other filesystems depend on mpath0 for this example config, the system is able to boot, but lacks swap due to the missing swap device. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le targetmilestone-inin14044 -- ISST-LTE: root mpath device unavailable after installation https://bugs.launchpad.net/bugs/1526984 You received this bug notification because you are a member
[Bug 1526984] Re: ISST-LTE: root mpath device unavailable after installation
** Package changed: ubuntu => multipath-tools (Ubuntu) -- 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/1526984 Title: ISST-LTE: root mpath device unavailable after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1526984/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527306] [NEW] Sync freeipmi 1.4.11-1 (main) from Debian unstable (main)
Public bug reported: Please sync freeipmi 1.4.11-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Don't probe the legacy SMBIOS address in /dev/mem on ARM platforms. (LP: #1499838) * Don't probe the legacy SMBIOS address in /dev/mem on ARM platforms. (LP: #1499838) * No-change rebuild for the libgcrypt20 transition. * No-change rebuild for the libgcrypt20 transition. * debian/patches/freeipmi-uefi.patch: Fix ipmi-locate on non ia64 architectures. (LP: #1359285) * debian/patches/freeipmi-uefi.patch: Fix ipmi-locate on non ia64 architectures. (LP: #1359285) * debian/patches/Retry-ssif-reads-as-needed.patch: Retry SSIF reads as needed, LP: #1324992 * Use dh-autoreconf to update libtool for ppc64el. * Fix dso linking on the convenience library. * Use dh-autoreconf to update libtool for ppc64el. * Fix dso linking on the convenience library. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * Resolve outstanding MIR issues, LP: #1052056 [ Andres Rodriguez ] * debian/rules: Build with "-pie,-bindnow" * debian/patches/0002_excel_when_opening_tmp.patch: Open files with O_EXCL. [ Dave Walker (Daviey) ] * debian/patches/fix-Wunused-result.patch: Resolve -Wunused-result's warnings, by checking for non-0 return. * Resolve outstanding MIR issues, LP: #1052056 [ Andres Rodriguez ] * debian/rules: Build with "-pie,-bindnow" * debian/patches/0002_excel_when_opening_tmp.patch: Open files with O_EXCL. [ Dave Walker (Daviey) ] * debian/patches/fix-Wunused-result.patch: Resolve -Wunused-result's warnings, by checking for non-0 return. The ubuntu changes either don't apply any longer due to upstream code refactoring (as in fix-Wunused-result.patch) or have been upstreamed already (0002_excel_when_opening_tmp.patch, dso-linking.patch, Fix-ipmi-locate-probing-issue-on-arm32-systems.patch, Fix-probing-issue-on-arm64-systems.patch, freeipmi-uefi.patch, Retry-ssif-reads-as-needed.patch). As of now only d/p/deb_bmc-watchdog_noRUN is required. Debian still carries 0001-Fix-Wformat-security-warnings.patch and up_fixmanpages, but those don't seem to be used during the package build. Changelog entries since current xenial version 1.1.5-3ubuntu7: freeipmi (1.4.11-1) unstable; urgency=medium * [186d83b] Merge tag 'upstream/1.4.11' Upstream version 1.4.11 * [95cfc3a] Updating symbols file. -- Bernd ZeimetzWed, 25 Nov 2015 21:40:35 +0100 freeipmi (1.4.9-1) unstable; urgency=medium * Fresh upstream release - removes duplicate entry from manpage (Closes: #781633) -- Yaroslav Halchenko Wed, 01 Jul 2015 09:52:35 -0400 freeipmi (1.4.5-3) unstable; urgency=medium * ACK and re-include NMU 1.4.4-1.2 -- Yaroslav Halchenko Wed, 08 Oct 2014 10:15:25 -0400 freeipmi (1.4.5-2) unstable; urgency=medium * Return to using /etc/logrotate.d/bmc-watchdog (Closes: #763136) -- Ferenc Wágner Tue, 07 Oct 2014 10:21:42 +0200 freeipmi (1.4.5-1) unstable; urgency=medium * [7e02411b] Merge tag 'upstream/1.4.5' Upstream version 1.4.5 -- Bernd Zeimetz Sun, 05 Oct 2014 14:08:36 +0200 freeipmi (1.4.4-1.2) unstable; urgency=medium * Non-maintainer upload. * Fix debian/libipmimonitoring5a.symbols after incomplete SONAME bump (Closes: #760920) -- Jonathan Wiltshire Tue, 09 Sep 2014 14:33:33 +0100 freeipmi (1.4.4-1.1) unstable; urgency=medium * Non-maintainer upload. * Add postinsts to replace /usr/share/doc/* with a symlink (Closes: #691439) -- Jonathan Wiltshire Sun, 07 Sep 2014 13:09:22 +0100 freeipmi (1.4.4-1) unstable; urgency=low [ Tollef Fog Heen ] * New upstream release - bump sonames - new tool: ipmi-config - refresh quilt patches - upstream dropped freeipmi-bmc-watchdog logrotate.d snippet, reintroduce as a Debian patch. * Add freeipmi-ipmiseld package. * Adjust dh_fixperms_override call to only be called on binary-indep. -- Yaroslav Halchenko Fri, 15 Aug 2014 09:23:03 -0400 freeipmi (1.1.6-1) experimental; urgency=low * [35d19e11] Merge tag 'upstream/1.1.6' Upstream version 1.1.6 * [b343fe99] Add myself to Uploaders. * [b7ece9fc] Refreshing patches, dropping those which were applied upstream. -- Bernd Zeimetz Fri, 03 Aug 2012 15:31:39 +0200 freeipmi (1.1.5-4) experimental; urgency=low [ Ferenc Wágner ] * Refresh lintian overrides * Fix typo (meta-package) in control file found by lintian * New quilt patch to fix upstream typos found by lintian * debian/control: - remove duplicate Section fields - add myself to Uploaders - add ipmi-pet to freeipmi-tools
[Bug 1488453] Update Released
The verification of the Stable Release Update for openhpi has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1488453 Title: Package postinst always fail on first install when using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openhpi/+bug/1488453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1488453] Re: Package postinst always fail on first install when using systemd
This bug was fixed in the package openhpi - 2.14.1-1.3ubuntu2.1 --- openhpi (2.14.1-1.3ubuntu2.1) vivid-proposed; urgency=medium * debian/openhpid.service: add systemd service file (LP: #1488453) -- Scott MoserThu, 01 Oct 2015 13:52:13 -0400 ** Changed in: openhpi (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1488453 Title: Package postinst always fail on first install when using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openhpi/+bug/1488453/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1526127] Re: node install error Unexpected error command: ['curtin', 'block-meta', 'simple']
fix committed in revno 322. ** Changed in: curtin Importance: Undecided => Medium ** Changed in: curtin Status: Confirmed => Fix Committed ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New => Confirmed ** Changed in: curtin (Ubuntu) Importance: Undecided => Medium -- 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/1526127 Title: node install error Unexpected error command: ['curtin', 'block-meta', 'simple'] To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1526127/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1460164] Re: upgrade of openvswitch-switch can sometimes break neutron-plugin-openvswitch-agent
FYI today's openvswitch-switch upgrade triggered a cluster-wide outage on one (or more) of our production openstacks. ** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1460164 Title: upgrade of openvswitch-switch can sometimes break neutron-plugin- openvswitch-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1460164/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527079] Re: Linux agent 2.0.14 may encounter unhandled error and exit accidently with Ubuntu 12.04, 14.04.
The SRU for 2.1.2 has been withdrawn at the request of Microsoft for Trusty and Vivid; the ETA for release of 2.1.x to Trusty and Vivid is currently unknown. Reopening this bug as confirmed. ** Changed in: walinuxagent (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1527079 Title: Linux agent 2.0.14 may encounter unhandled error and exit accidently with Ubuntu 12.04, 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1527079/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527341] [NEW] euca-bundle-image does not support ppc64le arch
Public bug reported: 2015-12-17 09:23:00.365 | ++ euca-bundle-image -r ppc64le -i /opt/stack/new/devstack/files/images/cirros-d150604-ppc64le-uec/cirros-d150604-ppc64le-vmlinuz --kernel true -d /opt/stack/new/devstack/files/images/s3-materials/cirros-d150604 2015-12-17 09:23:00.554 | usage: euca-bundle-image -i FILE [-p PREFIX] [-d DIR] -r 2015-12-17 09:23:00.555 | {i386,x86_64,armhf,ppc,ppc64} [-k FILE] [-c FILE] 2015-12-17 09:23:00.555 | [--ec2cert FILE] [-u ACCOUNT] [--kernel IMAGE] 2015-12-17 09:23:00.555 | [--ramdisk IMAGE] 2015-12-17 09:23:00.555 | [-B VIRTUAL1=DEVICE1,VIRTUAL2=DEVICE2,...] 2015-12-17 09:23:00.555 | [--productcodes CODE1,CODE2,...] 2015-12-17 09:23:00.555 | [--image-size IMAGE_SIZE] [--region USER@REGION] 2015-12-17 09:23:00.555 | [--debug] [--debugger] [--version] [-h] 2015-12-17 09:23:00.555 | euca-bundle-image: error: argument -r/--arch: invalid choice: 'ppc64le' (choose from 'i386', 'x86_64', 'armhf', 'ppc', 'ppc64') Required for Devstack (under lib/tempest) to upload and configure CirrOS image for ppc64le (Power Little-Endian) architecture. ** Affects: euca2ools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/1527341 Title: euca-bundle-image does not support ppc64le arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/1527341/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527362] [NEW] source-directory interfaces.d causes crash
Public bug reported: # virsh iface-list error: Failed to list interfaces error: internal error: failed to get number of host interfaces: unspecified error - errors in loading some config files root@noc1:/etc/libvirt/hooks# more /etc/network/interfaces source-directory interfaces.d # cat /etc/network/interfaces source-directory /etc/network/interfaces.d Also fails if: # cat /etc/network/interfaces source-directory interfaces.d Change the file as follows, all good. # cat interfaces auto lo iface lo inet loopback root@noc1:/etc/network# virsh iface-list Name State MAC Address --- lo active 00:00:00:00:00:00 However the source-directory facility is important to maintaining advanced networks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libnetcf1 1:0.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Dec 17 12:45:52 2015 InstallationDate: Installed on 2014-03-20 (636 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netcf UpgradeStatus: Upgraded to trusty on 2014-04-24 (602 days ago) ** Affects: netcf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1527362 Title: source-directory interfaces.d causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1527362/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1523715] Re: [SRU] update walinuxagent to 2.1.2 to fix docker extension and enable AzureStack
This bug was fixed in the package walinuxagent - 2.1.2-0ubuntu1~15.10.1 --- walinuxagent (2.1.2-0ubuntu1~15.10.1) wily; urgency=medium * Backport to 15.10 (LP: #1523715). -- Ben HowardWed, 09 Dec 2015 08:52:53 -0700 ** Changed in: walinuxagent (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1523715 Title: [SRU] update walinuxagent to 2.1.2 to fix docker extension and enable AzureStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1523715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527306] Re: Sync freeipmi 1.4.11-1 (main) from Debian unstable (main)
Discussed this with Tiago, and while the patches against upstream should be dropped, there is still an Ubuntu change to debian/rules (DEB_BUILD_MAINT_OPTIONS=hardening=+pie,+bindnow) which we should retain. So this becomes a merge after all, not a sync. ** Changed in: freeipmi (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1527306 Title: Sync freeipmi 1.4.11-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1527306/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1523715] Update Released
The verification of the Stable Release Update for walinuxagent has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1523715 Title: [SRU] update walinuxagent to 2.1.2 to fix docker extension and enable AzureStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1523715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
FYI, I ran into this trying to use snapcraft in an armhf schroot. AIUI, ubuntu-snappy will need to be rebuilt against golang 2:1.5.1-0ubuntu2.1 for snapcraft to be able to run 'snappy build' in the schroot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
Does it need rebuilding? I believe this patch is against the go-runtime so as long as the correct runtime version is installed this _should_ work. But I'll defer to @mwhudson. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501651] Re: ARM chroot issues: fatal error: rt_sigaction failure
It needs rebuilding. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1501651 Title: ARM chroot issues: fatal error: rt_sigaction failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1501651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 40189] Re: autofs needs to be restarted to pick up some shares
This is happening with us on Ubuntu 14.04.3 authenticating against ldap using sssd. I have changed my /etc/init/autofs.conf as recommended by Ruben (above #43) and it works for me as well. -- 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/40189 Title: autofs needs to be restarted to pick up some shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Ubuntu-server-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
I edited the description in line to make it mostly in line with the SRU wiki. It's hard to provide a test case without having a full ldap client and server configuration, plus an NFS system. I don't have access to the server side configs so I can't provide those. What extra information is necessary to get this into the Wily repository? ** Description changed: I'm running Wily Beta 2, updated to the latest packages in the wily repository, with autofs-ldap using mounts stored in LDAP. On startup systemd immediately puts autofs into a failed state as it segfaults when reading the auto.master. Autofs & autofs-ldap version is 5.1.1-1ubuntu2. The log in journalctl looks like this: Oct 05 15:47:45 autofs[2232]: * Starting automount... Oct 05 15:47:45 automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master Oct 05 15:47:45 automount[2240]: using kernel protocol version 5.02 Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: spawn_mount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: spawn_umount: mtab link detected, passing -n to mount Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry /net Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable Oct 05 15:47:45 automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d Oct 05 15:47:45 automount[2240]: lookup_read_master: lookup(file): read entry +auto.master Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master files auto.master Oct 05 15:47:45 automount[2240]: parse_init: parse(sun): init gathered global options: (null) Oct 05 15:47:45 automount[2240]: lookup_nss_read_master: reading master ldap auto.master Oct 05 15:47:45 kernel: automount[2240]: segfault at 0 ip 7fb87ade5bcb sp 7ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000] Oct 05 15:47:47 autofs[2232]: ...fail! Oct 05 15:47:47 systemd[1]: autofs.service: Control process exited, code=exited status=1 This occurs whenever the service is started with the line in auto.master which loads the ldap mounts. The line which causes the issue is "+ldap:automountMapName=auto.master.linux,ou=automount,ou=,ou=,o=,dc=,dc=com", and this configuration worked on 14.04, 14.10 and 15.04. + + [Impact] This bug prevents the autofs-ldap module from loading, and + causes it to segfault on startup. The proposed fix allows the module to + load normally. The fix initialises configuration cache before it is + first used (it is the access to the uninitialised cache which causes the + segfault). + + [Test Case] Install the autofs-ldap package and have it read an + automount map from LDAP. The necessary auto.master & ldap.conf + configuration is dependent on the LDAP server that provides the + automount maps. + + [Regression Potential] Given the shipped package does not load at all, + it can't be a regression on the shipped binary. -- 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 1473691] Re: Update to latest upstream stable release (3.5)
Note that the Ubuntu packages have had CVE-2014-7141 and CVE-2014-7142 fixed; CVE-2014-6270 is still open. We've rated CVE-2014-6270 as a low priority issue and will update it when a higher priority issue is found. http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-7141.html http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-7142.html http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-6270.html Thanks -- 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/1473691 Title: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] Re: ssh-keygen ignores $HOME
"dpkg -s openssh-client" lists "Homepage: http://www.openssh.org/;. That's usually the best way. From there I see they have instructions at http://www.openssh.com/report.html. I hope this helps! -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Branch linked: lp:~xianghui/ubuntu/trusty/neutron/lp1318721 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Branch linked: lp:~xianghui/ubuntu/trusty/oslo.messaging/lp1318721 ** Branch unlinked: lp:ubuntu/trusty-proposed/oslo.messaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527105] Re: Performance: drop HANDLE_BLOCK_INTERRUPTIONS support
Hi, thanks for the quick response. I'm more than happy for this to wait for Xenial. I wasn't aware there was going to be a 5.7. The page for 5.7 on the PHP wiki suggests that it was a proposal that wasn't accepted: https://wiki.php.net/rfc/php57 If I'm wrong about this then I'm happy to work with upstream to get it into 5.7, but it looks like they want all changes to go into php7 instead. If you're referring to php7, then yes, this stuff does go away in PHP7. However, I think there will still be a lot of people on php5 for some time (think how long people stayed with php4!), so it'd be nice to have that perform better. I accept that there is risk associated with taking this patch. For two reasons, I think the risk is minimal. Firstly, I would be very surprised if people were compiling their custom server backends against Ubuntu's source tree: I'd expect they'd compile against mainline. Secondly, even if they compiled against Ubuntu, they would need to depend on HANDLE_BLOCK_INTERRUPTIONS to experience an issue. Of all the server APIs ever bundled with PHP, only Apache1 ever provided these hooks. All of the (many!) other servers that PHP5 provided support for didn't use these hooks. If it were a 1 or 2% speed boost, I'd agree that it's not worth it. However, given that it's closer to 5%, I think it's worth the work to get it in. Thanks again, and I'm happy to address any further concerns you have. -- 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/1527105 Title: Performance: drop HANDLE_BLOCK_INTERRUPTIONS support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1527105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] Re: ssh-keygen ignores $HOME
Thank you for taking the time to report this bug and helping to make Ubuntu better. I understand that shells generally expand ~ to $HOME, but I'm not sure that automatically means the documentation is wrong, though I can see how it could have misled you in this case. I'm also not sure that there is consensus that changing $HOME should automatically change all program behaviour, since as you point out nss (eg. getent) will still look up /etc/passwd to find a different home directory. I'd expect that changing one without changing the other would produce inconsistent results as you have discovered. In any case, that is just my opinion. I doubt we'd carry a patch in Ubuntu to adjust this behaviour, so the best thing for you to do if you want to make any progress on this is to report it to upstream and see what they say. If you do, please link to your report here so others can follow. I'm marking this bug Won't Fix in Ubuntu because I don't think we should carry a patch and I don't think it's likely to change any time soon, so might as well set expectations correctly. But if it changes upstream or in Debian, then Ubuntu will follow by default. ** Tags added: needs-upstream-report ** Changed in: openssh (Ubuntu) Status: New => Won't Fix -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] Re: ssh-keygen ignores $HOME
PS. it's also valid to say that the documentation should at least be clarified, but I think my answer is the same in this case: it should go upstream and we won't carry a patch, since the benefit doesn't justify the additional maintenance burden in doing so. -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527105] Re: Performance: drop HANDLE_BLOCK_INTERRUPTIONS support
Thank you for taking the time to report this bug and helping to make Ubuntu better. If upstream don't consider this appropriate for the 5.6 branch then I am hesitant to include it in Ubuntu. In any case, I expect 5.7 to release in Xenial so the point could be moot for Xenial. This isn't a certainty yet though, and I'd certainly be happier carrying this in Xenial than in previous releases. For previous Ubuntu releases, we do as much as possible to minimise regression risk, so again I'm doubtful that this is justified. Users who want the speed boost can upgrade to Xenial and 5.7 when it is released, and in general this is the advertised path to get improvements, whereas stable releases are expected to be stable. See https://wiki.ubuntu.com/StableReleaseUpdates for our policy. > nor does it have any custom server APIs Is it possible that users will have third party custom compiled things here? This isn't by any means a final decision and I welcome further discussion on this. My concern is that any change carries risk, and I'm not sure a performance boost is worth that risk. Most users don't require that since they are already deployed, and soon I'd expect new deployments to be using Xenial where the patch is applied anyway. ** Changed in: php5 (Ubuntu) Status: New => Triaged ** Changed in: php5 (Ubuntu) Importance: Undecided => Medium -- 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/1527105 Title: Performance: drop HANDLE_BLOCK_INTERRUPTIONS support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1527105/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] [NEW] RPC timeout in all neutron agents
You have been subscribed to a public bug: In the logs the first traceback that happen is this: [-] Unexpected exception occurred 1 time(s)... retrying. Traceback (most recent call last): File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/excutils.py", line 62, in inner_func return infunc(*args, **kwargs) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 741, in _consumer_thread File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 732, in consume @excutils.forever_retry_uncaught_exceptions File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 660, in iterconsume try: File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 590, in ensure def close(self): File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 531, in reconnect # to return an error not covered by its transport File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 513, in _connect Will retry up to self.max_retries number of times. File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py", line 150, in reconnect use the callback passed during __init__() File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", line 508, in declare self.queue_bind(nowait) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", line 541, in queue_bind self.binding_arguments, nowait=nowait) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", line 551, in bind_to nowait=nowait) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/channel.py", line 1003, in queue_bind (50, 21), # Channel.queue_bind_ok File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/abstract_channel.py", line 68, in wait return self.dispatch_method(method_sig, args, content) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/abstract_channel.py", line 86, in dispatch_method return amqp_method(self, args) File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/channel.py", line 241, in _close reply_code, reply_text, (class_id, method_id), ChannelError, NotFound: Queue.bind: (404) NOT_FOUND - no exchange 'reply_8f19344531b448c89d412ee97ff11e79' in vhost '/' Than an RPC Timeout is raised each second in all the agents ERROR neutron.agent.l3_agent [-] Failed synchronizing routers TRACE neutron.agent.l3_agent Traceback (most recent call last): TRACE neutron.agent.l3_agent File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/agent/l3_agent.py", line 702, in _rpc_loop TRACE neutron.agent.l3_agent self.context, router_ids) TRACE neutron.agent.l3_agent File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/agent/l3_agent.py", line 79, in get_routers TRACE neutron.agent.l3_agent topic=self.topic) TRACE neutron.agent.l3_agent File "/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/proxy.py", line 130, in call TRACE neutron.agent.l3_agent exc.info, real_topic, msg.get('method')) TRACE neutron.agent.l3_agent Timeout: Timeout while waiting on RPC response - topic: "q-l3-plugin", RPC method: "sync_routers" info: "" This actually make the agent useless until they are all restarted. An analyze of what's going on coming soon :) --- [Impact] This patch addresses an issue when a RabbitMQ cluster node goes down, OpenStack services try to reconnect to another RabbitMQ node and then re-create everything from scratch , and due to the 'auto-delete' flag is set, race condition happened between re-create and delete on Exchange, Queues, Bindings, which caused nova-compute and neutron agents are down. [Test Case] Note steps are for trusty-icehouse, including latest oslo.messaging library (1.3.0-0ubuntu1.2 at the time of this writing). Deploy an OpenStack cloud w/ multiple rabbit nodes and then abruptly kill one of the rabbit nodes (e.g. sudo service rabbitmq-server stop, etc). Observe that the nova services and neutron agents do detect that the node went down and report that they are reconnected, but messages are still reporting as timed out, nova service-list/neutron agent-list still reports compute and agents as down, etc. [Regression Potential] None. ** Affects: neutron Importance: Undecided Status: Invalid ** Affects: oslo.messaging Importance: Medium Assignee: Dr. Jens Rosenboom (j-rosenboom-j)
[Bug 1527194] [NEW] package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 failed to install/upgrade: el subprocés s'ha instaŀlat el script post-installation retornà el codi d'eixida d'error 1
Public bug reported: no ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-56-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Thu Dec 17 11:29:34 2015 ErrorMessage: el subprocés s'ha instaŀlat el script post-installation retornà el codi d'eixida d'error 1 InstallationDate: Installed on 2015-09-02 (105 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ib_logfile1', 'ib_logfile0', 'ibdata1', 'mysql', 'performance_schema', 'debian-5.5.flag'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-56-generic root=UUID=50461cf4-ca66-4c9b-9064-17490e69d13f ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: mysql-5.5 Title: package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 failed to install/upgrade: el subprocés s'ha instaŀlat el script post-installation retornà el codi d'eixida d'error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (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 mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1527194 Title: package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 failed to install/upgrade: el subprocés s'ha instaŀlat el script post- installation retornà el codi d'eixida d'error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1527194/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1358835] Comment bridged from LTC Bugzilla
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT--- Verified: gcc test.c -ldl -o test ubuntu@vm19:~$ ./test 80 80 cpu 80 belongs to node 2 ubuntu@vm19:~$ numactl -H available: 4 nodes (0-3) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 node 0 size: 969 MB node 0 free: 445 MB node 1 cpus: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 node 1 size: 1022 MB node 1 free: 777 MB node 2 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 node 2 size: 1022 MB node 2 free: 37 MB node 3 cpus: 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 node 3 size: 1017 MB node 3 free: 907 MB node distances: node 0 1 2 3 0: 10 40 40 40 1: 40 10 40 40 2: 40 40 10 40 3: 40 40 40 10 ubuntu@vm19:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS" --- Comment From mainam...@in.ibm.com 2015-03-19 05:43 EDT--- The test described in the bug fails in Ubuntu 14.04.2. The following packages were tried as well: libnuma1 2.0.9~rc5-1ubuntu3 and numactl 2.0.9~rc5-1ubuntu3 In all cases the test failed. The efix for 14.04.1 provided by Thierry Fauck worked but it was not used in 14.04.02 --- Comment From mainam...@in.ibm.com 2015-03-25 10:41 EDT--- Any updates on this? --- Comment From thierry.fa...@fr.ibm.com 2015-04-08 07:54 EDT--- Commit 573609fb2711b6c09090cc3fef9a771ae9eb246b sent to maintainers >From 573609fb2711b6c09090cc3fef9a771ae9eb246b Mon Sep 17 00:00:00 2001 From: Thierry FAUCK - IBM LTCDate: Tue, 7 Apr 2015 17:53:34 +0200 Subject: [PATCH] libnuma.so On ppc64el, cpu number are not contigous Commit 32075635db57c3d5efe12f8fb569af857e01ccad issuea warning message /sys not mounted when it find a non existent cpu number, and that's the default for multinode on ppc64el bare metal installed system. This patch removes the message when the /sys entry doesn't exist, but use the return code. Signed-off-by: Thierry FAUCK - IBM LTC modified: libnuma.c --- libnuma.c | 22 +- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/libnuma.c b/libnuma.c index 3717d5b..98aa10f 100644 --- a/libnuma.c +++ b/libnuma.c @@ -1276,11 +1276,13 @@ numa_node_to_cpus_v1(int node, unsigned long *buffer, int bufferlen) sprintf(fn, "/sys/devices/system/node/node%d/cpumap", node); f = fopen(fn, "r"); if (!f || getdelim(, , '\n', f) < 1) { - numa_warn(W_nosysfs2, - "/sys not mounted or invalid. Assuming one node: %s", + if (f) { + numa_warn(W_nosysfs2, + "/sys not mounted or invalid. Assuming one node: %s", strerror(errno)); - numa_warn(W_nosysfs2, - "(cannot open or correctly parse %s)", fn); + numa_warn(W_nosysfs2, + "(cannot open or correctly parse %s)", fn); + } bitmask.maskp = (unsigned long *)mask; bitmask.size = buflen_needed * 8; numa_bitmask_setall(); @@ -1355,11 +1357,13 @@ numa_node_to_cpus_v2(int node, struct bitmask *buffer) sprintf(fn, "/sys/devices/system/node/node%d/cpumap", node); f = fopen(fn, "r"); if (!f || getdelim(, , '\n', f) < 1) { - numa_warn(W_nosysfs2, - "/sys not mounted or invalid. Assuming one node: %s", - strerror(errno)); - numa_warn(W_nosysfs2, - "(cannot open or correctly parse %s)", fn); + if (f) { + numa_warn(W_nosysfs2, + "/sys not mounted or invalid. Assuming one node: %s", + strerror(errno)); + numa_warn(W_nosysfs2, + "(cannot open or correctly parse %s)", fn); + } numa_bitmask_setall(mask); err = -1; } -- 1.7.9.5 --- Comment From amda...@us.ibm.com 2015-06-01 20:02 EDT--- Has this patch been accepted by maintainers? The Canonical status is fix released. Is there a fix that should be pulled and tested? -- 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/1358835 Title: numa_node_of_cpu() returns warning when cpu_index > 79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1358835/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 1527105] [NEW] Performance: drop HANDLE_BLOCK_INTERRUPTIONS support
You have been subscribed to a public bug by Robie Basak (racb): Dropping HANDLE_BLOCK_INTERRUPTIONS, which is only used by Apache 1, and is dropped in PHP7, leads to a 4-6% speedup on artificial benchmarks and a measurable speedup on real world applications. I have written a patch to do this and submitted it upstream: https://github.com/php/php-src/pull/1532 The PHP folk are a little hesitant to merge it in case there's anyone downstream who has a custom server API that still uses the hooks. Ubuntu doesn't ship Apache 1, nor does it have any custom server APIs, so it's safe to be merged, giving all your users a speed boost. All the details and the patch are in the upstream submission, and I'm happy to answer any other questions or get it into whatever format is most useful for you. ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- Performance: drop HANDLE_BLOCK_INTERRUPTIONS support https://bugs.launchpad.net/bugs/1527105 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527044] [NEW] Update mutex from file to pthread
You have been subscribed to a public bug by Robie Basak (racb): The default Mutex implementation used by Ubuntu's Apache package is file locking. (See /etc/apache2/apache2.conf) This is slower than pthreads, especially when using mpm_prefork. The Apache project currently warns about pthreads being potentially dangerous.[1] However, Linux has supported robust pthreads for many years now,[2] so it's safe for Ubuntu to move to pthreads and reap the performance benefits. My tests on POWER8, VM and bare-metal, PHP and static files, show something like a 1.5% to 3.5% performance gain for a one-line config change. [1] https://httpd.apache.org/docs/trunk/mod/core.html#mutex [2] See this apache bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=58744 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: needs-upstream-report -- Update mutex from file to pthread https://bugs.launchpad.net/bugs/1527044 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527079] Re: Linux agent 2.0.14 may encounter unhandled error and exit accidently with Ubuntu 12.04, 14.04.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Looks like this is fixed upstream in 2.1.2 and this version is currently in the process of being backported to all releases, which is being tracked in bug 1523715. Since Xenial is already on 2.1.2, the correct bug status is Fix Released. Note that this doesn't reflect the status of existing supported releases. I won't create separate tasks to track the existing supported releases since they won't auto-close and due to bug 1523715 they will be fixed imminently anyway. ** Changed in: walinuxagent (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1527079 Title: Linux agent 2.0.14 may encounter unhandled error and exit accidently with Ubuntu 12.04, 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1527079/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1473691] Re: Update to latest upstream stable release (3.5)
** Information type changed from Public to Public Security -- 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/1473691 Title: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527162] Re: ssh-keygen ignores $HOME
Where is upstream? And how might I find that out for myself? -- 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/1527162 Title: ssh-keygen ignores $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1527162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527044] Re: Update mutex from file to pthread
Thank you for taking the time to report this bug and helping to make Ubuntu better. We could fix this in Xenial, thanks. I appreciate your performance testing report, but is there anything from upstream that documents that pthread mutexes with mpm_prefork are expected to be faster? This should be reported to Debian too, so I'll leave a tag for that. Again, we'd prefer to stay as close to Debian as possible. ** Tags added: needs-upstream-report ** Changed in: apache2 (Ubuntu) Status: New => Triaged ** Changed in: apache2 (Ubuntu) Importance: Undecided => Medium -- 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/1527044 Title: Update mutex from file to pthread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1527044/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Package changed: ubuntu => neutron (Ubuntu) ** Changed in: neutron (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: neutron (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318317] Re: openipmi startup script removes kernel modules
Oliver, Tore & Jeremy, I'm taking a look at this issue now, and just wanted to confirm that you've not modified /etc/default/openipmi in your setups (except as the noted workaround by Jeremy)? -- 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/1318317 Title: openipmi startup script removes kernel modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1318317/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs