[Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
Yes, I thought it would be more clear cause I can't change the title of this bug. Once the patch is applied and updated meta-packages pushed both bugs could be safely closed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 819251] Re: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
[Expired for dbconfig-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbconfig-common (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/819251 Title: package phpmyadmin 4:3.3.10-1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/819251/+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 569313] Re: package bacula-director upgrade failed because it couldn't connect to mysql-server
[Expired for dbconfig-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbconfig-common (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/569313 Title: package bacula-director upgrade failed because it couldn't connect to mysql-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/569313/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I can reproduce with corosync 2.3.3. Using corosync 2.3.4 from ppa:mariosplivalo/corosync on trusty I've not been able to reproduce on 2 tries. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1449056] Re: rabbitmq not ready after restart
Reviewed: https://review.openstack.org/186641 Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=6bc905c3488a93fa87776bcd0af7e362a90b082f Submitter: Jenkins Branch:master commit 6bc905c3488a93fa87776bcd0af7e362a90b082f Author: Tony Breeds t...@bakeyournoodle.com Date: Fri May 15 12:51:43 2015 +1000 Change the restart_rpc_backend loop to accomodate async rabbitmq Some distros have converted to systemd for starting RabbitMQ. This has resulted in: --- [Call Trace] ./stack.sh:904:restart_rpc_backend /home/stack/projects/openstack/openstack-dev/devstack/lib/rpc_backend:201:die [ERROR] /home/stack/projects/openstack/openstack-dev/devstack/lib/rpc_backend:201 Failed to set rabbitmq password Error on exit World dumping... see /opt/stack/logs/worlddump-2015-05-29-031618.txt for details --- Because 'restart_service rabbitmq-server' returns before the server is ready to accept connections. Alter the retry loop to only restart the rabbitmq-server every second time through the loop. Allowing time for the slow rabbit to start. Closes-Bug: 1449056 Change-Id: Ibb291c1ecfd109f9ed10b5f194933364985cc1ce ** Changed in: devstack Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/1449056 Title: rabbitmq not ready after restart To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1449056/+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 1442797] Re: add patches to support ppc64el better
We have better versions of these patches in progress. Once they are upstream we will update the bug. -- 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/1442797 Title: add patches to support ppc64el better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1442797/+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 1462001] Re: [needs-packaging] 1.22.5 is not packaged in trusty
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Summary changed: - 1.22.5 is not packaged in trusty + [needs-packaging] 1.22.5 is not packaged in trusty ** Changed in: juju-core (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1462001 Title: [needs-packaging] 1.22.5 is not packaged in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+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 1461012] Re: Hugepage and KSM not configured correctly under systemd
This should be fixed in 1:2.3+dfsg-4ubuntu1. I did not actually add a systemd unit, but rather fixed the sysv unit. On my tests systems /run/hugepages was again mounted. ** Changed in: qemu (Ubuntu) Status: Confirmed = Fix Released ** Changed in: qemu (Ubuntu Vivid) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1461012 Title: Hugepage and KSM not configured correctly under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1461012/+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 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
This should be fixed in 1:2.3+dfsg-4ubuntu1 ** Changed in: qemu (Ubuntu Wily) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+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 1371634] Re: block devices appear twice
** Branch linked: lp:~strikov/curtin/multipath-2 -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1432786] Re: upgrade of ceph in vivid breaks qemu-system-arm
The patch was merged to Ceph master upstream in 35c5fd0091fc4d63b21207fb94e46b343519fd56 (https://github.com/ceph/ceph/pull/4839) ** Bug watch added: Red Hat Bugzilla #186 https://bugzilla.redhat.com/show_bug.cgi?id=186 ** Also affects: ceph (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=186 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1432786 Title: upgrade of ceph in vivid breaks qemu-system-arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1432786/+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 1371634] Re: block devices appear twice
I tried following the above workaround on the IBM Power 8 twice on new deployments. Attached is the log. ** Attachment added: multipath.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1462001] Re: 1.22.5 is not packaged in trusty
** Description changed: We're now in a position to have 1.22.5 enter trusty-proposed. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. + [Devel Fix] + [sinzui] Prepare source package, and diffs. + [rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid. + [Stable Fix] - Full backport of new upstream release to trust. + Full backport of new upstream release to trust, utopic, vivid, . [Pre-QA tasks] - [person] Upload to the current LTS release (trusty-proposed): TODO + [rbasak] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against trusty-proposed: TODO [sinzui] Test juju-deployer against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO ** Description changed: We're now in a position to have 1.22.5 enter trusty-proposed. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Devel Fix] + [sinzui] Prepare source package, and diffs. [rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid. [Stable Fix] Full backport of new upstream release to trust, utopic, vivid, . [Pre-QA tasks] [rbasak] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against trusty-proposed: TODO [sinzui] Test juju-deployer against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1462001 Title: 1.22.5 is not packaged in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+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 1447200] Re: juju-core 1.23.1 is not packaged in Ubuntu
** Changed in: juju-core (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1447200 Title: juju-core 1.23.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1447200/+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 1462001] [NEW] 1.22.5 is not packaged in trusty
Public bug reported: We're now in a position to have 1.22.5 enter trusty-proposed. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Development Fix] Upload of new upstream release with packaging review. [person] will remove the block-proposed tag when verification has passed, and then this update should migrate to trusty. [Stable Fix] Full backport of new upstream release. [Pre-QA tasks] [person] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against trusty-proposed: TODO [sinzui] Test juju-deployer against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: needs-packaging ** Tags added: needs-packaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1462001 Title: 1.22.5 is not packaged in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+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 1462001] Re: 1.22.5 is not packaged in trusty
** Description changed: We're now in a position to have 1.22.5 enter trusty-proposed. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. - [Development Fix] - - Upload of new upstream release with packaging review. [person] will - remove the block-proposed tag when verification has passed, and then - this update should migrate to trusty. - [Stable Fix] - Full backport of new upstream release. + Full backport of new upstream release to trust. [Pre-QA tasks] [person] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against trusty-proposed: TODO [sinzui] Test juju-deployer against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1462001 Title: 1.22.5 is not packaged in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+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 1460337] Re: tempest_lib.auth not compatible with original tempest.auth
if tempest.con exist at etc director or TEMPEST_CONFIG and TEMPEST_CONFIG_DIR point to existing tempest.con then the client manager will be created. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tempest-lib in Ubuntu. https://bugs.launchpad.net/bugs/1460337 Title: tempest_lib.auth not compatible with original tempest.auth To manage notifications about this bug go to: https://bugs.launchpad.net/tempest/+bug/1460337/+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 1458323] Re: Asterisk crashes with default install because of pjsip
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: asterisk (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1458323 Title: Asterisk crashes with default install because of pjsip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+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 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted
** 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 squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1456662 Title: squid-deb-proxy fails to resolve dns entry : needs to be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+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 1342080] Re: glance api is tracebacking with error: [Errno 32] Broken pipe
** Also affects: python-glanceclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1342080 Title: glance api is tracebacking with error: [Errno 32] Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1342080/+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
Adding ppa:ubuntu-lxc/daily seems to solve the problem. -- 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 1451807] Re: mod-wsgi not working with Python 3.4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mod-wsgi (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/1451807 Title: mod-wsgi not working with Python 3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1451807/+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 1427406] Re: data corruption on arm64
** Branch linked: lp:~dannf/ubuntu/wily/mysql-5.6/lp1427406 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1427406 Title: data corruption on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1427406/+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 1461276] [NEW] off-by-one in LDIF length
You have been subscribed to a public bug by Robie Basak (racb): Would it be possible to include the patch for ITS#8003 in the next build of the 2.4.40 package? http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=c8353f7acdec4a42f537b0d475aaae005ba72363 It fixes a bug that causes slapd to crash when the audit log is enabled and a large base64-encoded attribute is printed. ** Affects: openldap (Ubuntu) Importance: High Status: New ** Tags: crash slapd -- off-by-one in LDIF length https://bugs.launchpad.net/bugs/1461276 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 1319145] Re: cannot use openstack python client libraries from python3
** Changed in: python-keystoneclient (Ubuntu) Assignee: (unassigned) = Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1319145 Title: cannot use openstack python client libraries from python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova-adminclient/+bug/1319145/+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 1371634] Re: block devices appear twice
** Description changed: - $ sudo blkid - /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 - /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap - /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 - /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap - /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 - /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + $ sudo blkid + /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 + /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap + /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 + /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap + /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 + /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: - sda - sdg - sdb - sdh + sda - sdg + sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. + + Related bugs: + * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: - linux-restricted-modules-3.13.0-35-generic N/A - linux-backports-modules-3.13.0-35-generic N/A - linux-firmware 1.127.6 + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1432062] Re: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers
** Description changed: If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed. If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support. - Those rules don't handle disk devices w/ spaces on their names/uuids/models very well.. + Those rules don't handle disk devices w/ spaces on their names/uuids/models very well.. That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example. Thus, the system fails to boot. There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled). Notice it's an acceptable case to install w/out multipath support, and enable it later for booting. Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example: - IBM IPR ( IBM IPR-0 5DB6F480 ) - - IBM VDASD ( AIX VDASD 00c96f074c00014bb8e713f0.14 ) + - IBM VDASD ( AIX VDASD 00c96f074c00014bb8e713f0.14 ) - QEMU HARDDISK ( QEMU QEMU HARDDISK serial ) So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot? For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install. + + Related bugs: + * bug 1371634: block devices appear twice -- 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/1432062 Title: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+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 1432062] Re: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers
Hi, Attached to bug 1371634 i added a script that shows a general issue with kpartx being called on files with spaces in them. Does that seem like a bug that should also be fixed? it shows itself with: $ img=/tmp/my.img; spacename=/dev/my space name; $ truncate --size=1G $img $ echo 2048, | sfdisk --force $img --unit S $ lodev=$(sudo losetup --find --show $img) $ echo $lodev /dev/loop0 $ sudo ln -sf $lodev $spacename $ ls -l $lodev $spacename brw-rw 1 root disk 7, 0 Jun 4 09:25 /dev/loop0 lrwxrwxrwx 1 root root 10 Jun 4 09:25 /dev/my space name - /dev/loop0 $ sudo kpartx -a -v $spacename device-mapper: reload ioctl on my\x20space\x20name1 failed: Invalid argument create/reload failed on my space name1 add map my space name1 (0:0): 0 2095104 linear /dev/my space name 2048 ## then clean up $ sudo losetup -d $lodev $ sudo rm $spacename $img -- 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/1432062 Title: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+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 1371634] Re: block devices appear twice
OK, so for trivial workaround fix, you can do:
a.) install with curtin as you have
b.) sudo apt-get install multipath-tools-boot
c.) printf defaults {\n\tuser_friendly_names yes\n}\n | sudo tee
/etc/multipath.conf
d.) sudo update-initramfs -u -k all
e.) sudo reboot
You'll come back up with multipath as the root device.
Oleg is working on a merge proposal for curtin that will do that by
default.
When the fix for bug 1432062 lands, then we wont even specifically need
the user_friendly_names patch.
--
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/1371634
Title:
block devices appear twice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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
