[Bug 1468293] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.2: openvswitch kernel module failed to build
*** This bug is a duplicate of bug 1369294 *** https://bugs.launchpad.net/bugs/1369294 ** This bug is no longer a duplicate of bug 1426994 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11, but version newer than 3.12.x is not supported] ** This bug has been marked a duplicate of bug 1369294 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/XXX/build is version XXX, but version newer than 3.12.x is not supported] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1468293 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.2: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1468293/+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 1450313] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
*** This bug is a duplicate of bug 1369294 *** https://bugs.launchpad.net/bugs/1369294 ** This bug is no longer a duplicate of bug 1426994 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11, but version newer than 3.12.x is not supported] ** This bug has been marked a duplicate of bug 1369294 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/XXX/build is version XXX, but version newer than 3.12.x is not supported] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1450313 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1450313/+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 1450312] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
*** This bug is a duplicate of bug 1369294 *** https://bugs.launchpad.net/bugs/1369294 ** This bug is no longer a duplicate of bug 1426994 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11, but version newer than 3.12.x is not supported] ** This bug has been marked a duplicate of bug 1369294 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/XXX/build is version XXX, but version newer than 3.12.x is not supported] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1450312 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1450312/+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 1440430] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
*** This bug is a duplicate of bug 1369294 *** https://bugs.launchpad.net/bugs/1369294 ** This bug is no longer a duplicate of bug 1426994 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11, but version newer than 3.12.x is not supported] ** This bug has been marked a duplicate of bug 1369294 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/XXX/build is version XXX, but version newer than 3.12.x is not supported] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1440430 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1440430/+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 1426994] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11
*** This bug is a duplicate of bug 1369294 *** https://bugs.launchpad.net/bugs/1369294 ** This bug has been marked a duplicate of bug 1369294 openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/XXX/build is version XXX, but version newer than 3.12.x is not supported] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1426994 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build [configure: error: Linux kernel in /lib/modules/3.13.0-46-generic/build is version 3.13.11, but version newer than 3.12.x is not supported] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1426994/+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 1471237] [NEW] Mongo causes juju to fail: bad record MAC
Public bug reported: This is a meta bug. mongo 2.6 can drop or corrupt connections. This bug will be fixed when either juju find a way to restore the connection, or a fixed mongodb is distributed and available to precise users and above. ** Affects: juju-core Importance: Medium Status: Triaged ** Affects: mongodb (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: mongodb reliability ** Also affects: mongodb (Ubuntu) Importance: Undecided Status: New ** Changed in: mongodb (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1471237 Title: Mongo causes juju to fail: bad record MAC To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1471237/+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 1449369] Re: backport patches of wala 2.0.12 2.0.13 for ubuntu 12.04
** Changed in: walinuxagent (Ubuntu) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu) Importance: Undecided = High ** Summary changed: - backport patches of wala 2.0.12 2.0.13 for ubuntu 12.04 + [SRU] Update WALinuxAgent to 2.0.13 ** Also affects: walinuxagent (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Wily) Importance: High Assignee: Ben Howard (utlemming) Status: New ** Also affects: walinuxagent (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: walinuxagent (Ubuntu Vivid) Importance: Undecided = Medium ** Changed in: walinuxagent (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: walinuxagent (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: walinuxagent (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: walinuxagent (Ubuntu Precise) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu Trusty) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu Utopic) Assignee: (unassigned) = Ben Howard (utlemming) ** Changed in: walinuxagent (Ubuntu Vivid) Assignee: (unassigned) = Ben Howard (utlemming) -- 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/1449369 Title: [SRU] Update WALinuxAgent to 2.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1449369/+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 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
On the other side I removed pm-utils from the system and there are a couple of remaining scripts in /etc/pm/sleep.d that are worth mentioning: * 10_grub-common * 10_unattended-upgrades-hibernate Thus, those packages are also affected by this bug I guess. ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - pm-suspend.log and pm-powersave.log not updated since upgrade to vivid + pm-suspend no longer run since upgrade to vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend no longer run since upgrade to vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455097/+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 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
I moved my script to systemd, adapted it following Martin's instructions in comment #5 and it just works as expected. Thanks a lot :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend no longer run since upgrade to vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455097/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
So it does appear that this a result of the openvswitch-switch service
taking a while to startup on boot/reboot. I have added some retry logic
to nova-compute and it appears that openvswitch is taking around 80s to
start:
neutron-ovs-cleanup start/pre-start, process 3055
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 1s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 3s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 3s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 5s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 5s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 7s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 7s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 9s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 9s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 11s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 11s
neutron-ovs-cleanup start/pre-start, process 3055
Attempting to start neutron-ovs-cleanup
start: Job is already running: neutron-ovs-cleanup
Recheck neutron-ovs-cleanup status in 13s
neutron-ovs-cleanup start/running
2015-07-03 17:51:40.660 15690 DEBUG nova.servicegroup.api [-] ServiceGroup
driver defined as an instance of db __new__
/usr/lib/python2.7/dist-packages/nova/servicegroup/api.py:65
2015-07-03 17:51:43.053 15690 INFO nova.openstack.common.periodic_task [-]
Skipping periodic task _periodic_update_dns because its interval is negative
2015-07-03 17:51:44.320 15690 DEBUG stevedore.extension [-] found extension
EntryPoint.parse('file = nova.image.download.file') _load_plugins
/usr/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-07-03 17:51:44.602 15690 DEBUG stevedore.extension [-] found extension
EntryPoint.parse('file = nova.image.download.file') _load_plugins
/usr/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-07-03 17:51:44.603 15690 INFO nova.virt.driver [-] Loading compute driver
'libvirt.LibvirtDriver'
I'll have an SRU patch up shortlty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1471022
Title:
[SRU] race between nova-compute and neutron-ovs-cleanup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Patch added: utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+attachment/4423972/+files/utopic.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1342083] Re: Failed to create chardev due to apparmor DENIED execute of /usr/lib/pt_chown
Ok, thanks - we will add that to the 1.2.16 merge, then we can SRU. Please note here if you need this SRU'd to vivid, or only to trusty. ** Changed in: libvirt (Ubuntu) Status: Incomplete = Triaged ** Also affects: libvirt (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1342083 Title: Failed to create chardev due to apparmor DENIED execute of /usr/lib/pt_chown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1342083/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Description changed: + [Impact] + This issue appears to be a consequence of https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572 where we added a 'wait-for-state running' to the nova-compute upstart so as to ensure that neutron-ovs-cleanup has finished before nova-compute starts. I have started to spot, however, that on some hosts (metal only) there is now a race between the two whereby nova-compute sometimes fails to start on system boot/reboot with the following in /var/log/upstart/nova- compute.log: ... libvirt-bin stop/waiting wait-for-state stop/waiting neutron-ovs-cleanup start/pre-start, process 3084 start: Job failed to start If I manually restart nova-compute all is fine. So this looks like a race between nova-compute's wait-for-state and neutron-ovs-cleanup's pre-start - start/running. + + The proposed solution here is add some retry logic to nova-compute + upstart job to tolerate neutron-ovs-cleanup not being able to start yet. + We, therefore, allow a certain number of retries, every other with an + incremented delay, before giving up and allowing nova-compute to start + anyway. If ovs-cleanup failed to start after what is a failry liberal + retry period, it is assumed to have failed altogether this making is + safe(ish) to start nova-compute. + + [Test Case] + + In one terminal (as root) do: + service neutron-ovs-cleanup stop; service openvswitch-switch stop; service nova-compute restart + + In another do: + sudo tail -F /var/log/upstart/nova-compute.log + + Observe the retries occurring + + Then do 'sudo service openvswitch-switch start' and observe nova-compute + retry and succeed. + + [Regression Potential] + + * If openvswitch-switch does not start within the max retries and + intervals nova-compute will start anyway and of ovs-cleanup were at some + point to run one would see the behaviour that LP 1420572 was intended to + resolve. It does not seem to make sense to wait indefinitely for ovs- + cleanup to be up and the coded interval is pretty liberal and should be + plenty enough. ** Changed in: nova (Ubuntu Trusty) Status: New = In Progress ** Changed in: nova (Ubuntu Utopic) Status: New = In Progress ** Changed in: nova (Ubuntu Vivid) Status: New = In Progress ** Changed in: nova (Ubuntu Trusty) Assignee: (unassigned) = Edward Hope-Morley (hopem) ** Changed in: nova (Ubuntu Utopic) Assignee: (unassigned) = Edward Hope-Morley (hopem) ** Changed in: nova (Ubuntu Vivid) Assignee: (unassigned) = Edward Hope-Morley (hopem) ** Description changed: [Impact] This issue appears to be a consequence of https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572 where we added a 'wait-for-state running' to the nova-compute upstart so as to ensure that neutron-ovs-cleanup has finished before nova-compute starts. I have started to spot, however, that on some hosts (metal only) there is now a race between the two whereby nova-compute sometimes fails to start on system boot/reboot with the following in /var/log/upstart/nova- compute.log: ... libvirt-bin stop/waiting wait-for-state stop/waiting neutron-ovs-cleanup start/pre-start, process 3084 start: Job failed to start If I manually restart nova-compute all is fine. So this looks like a race between nova-compute's wait-for-state and neutron-ovs-cleanup's pre-start - start/running. The proposed solution here is add some retry logic to nova-compute upstart job to tolerate neutron-ovs-cleanup not being able to start yet. We, therefore, allow a certain number of retries, every other with an incremented delay, before giving up and allowing nova-compute to start anyway. If ovs-cleanup failed to start after what is a failry liberal - retry period, it is assumed to have failed altogether this making is + retry period, it is assumed to have failed altogether thus making is safe(ish) to start nova-compute. [Test Case] In one terminal (as root) do: service neutron-ovs-cleanup stop; service openvswitch-switch stop; service nova-compute restart In another do: sudo tail -F /var/log/upstart/nova-compute.log Observe the retries occurring Then do 'sudo service openvswitch-switch start' and observe nova-compute retry and succeed. [Regression Potential] - * If openvswitch-switch does not start within the max retries and + * If openvswitch-switch does not start within the max retries and intervals nova-compute will start anyway and of ovs-cleanup were at some point to run one would see the behaviour that LP 1420572 was intended to resolve. It does not seem to make sense to wait indefinitely for ovs- cleanup to be up and the coded interval is pretty liberal and should be plenty enough. ** Description changed: [Impact] This issue appears to be a consequence of https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572 where we added a
Re: [Bug 1464278] Re: Qemu-Libgfapi: periodical shutdown of virtual machines.
Ok, you can get the CoreFile from that using apport-unpack: mkdir crashfiles; apport-unpack /var/crash/_usr_bin_qemu-system- x86_64.0.crash crashfiles Then you should be able to use the 'where' command in gdb gdb /usr/bin/qemu-system-x86_64 crashfiles/CoreDump (gdb) where to get more information. Please paste that information here. -- 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/1464278 Title: Qemu-Libgfapi: periodical shutdown of virtual machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1464278/+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 1449369] Re: [SRU] Update WALinuxAgent to 2.0.13
This bug was fixed in the package walinuxagent - 2.0.13-0ubuntu1 --- walinuxagent (2.0.13-0ubuntu1) wily; urgency=medium * New upstream release (LP: #1449369). * Rebased patches for 2.0.12 onto 2.0.13. -- Ben Howard ben.how...@ubuntu.com Thu, 02 Jul 2015 15:14:26 -0600 ** Changed in: walinuxagent (Ubuntu Wily) 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/1449369 Title: [SRU] Update WALinuxAgent to 2.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1449369/+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 1449369] Re: [SRU] Update WALinuxAgent to 2.0.13
** Description changed: + [SRU Justification] + WALinuxAgent prior to 2.0.13 will crash on large size VM's due to a race condition. Newer VM types and large VM's are affected. Further, + + [FIX] + WALinuxAgent 2.0.13 contains several fixes including: +- Handle http 410 returned by host +- Add support for http proxy +- Add support to execute CustomData after provisioning +- Add a udev rule for product-uuid +- Update service start/stop command for Ubuntu + + + [TEST CASES] + Test Case 1: + - Launch Ubuntu instance + - Upgrade walinuxagent from -proposed + - Check /var/log/waagent for errors + - Reboot + - Check /var/log/waagent.log for errors + - Confirm that /var/log/waagent.log is running + + Test Case 2: + - Shutdown instance from Test Case 1 + - Capture VM + - Launch new instance from Capture VM + - Confirm instance comes up with new identity + - Confirm /var/lib/waagent/SharedConfig.xml exists + - Confirm that waagent is running + + Test Case 3: + - Build new image from -proposed + - Boot new image + - Confirm that instance provisioned + + [RISK] + Limited to moderate. The update to 2.0.13 for 12.04 (currently at 2.0.8) contains new features, which are required for provisioning on newer VM types. Extensive testing of the new agent by both Microsoft and the Canonical Cloud Image has been and will be performed in order to capture any fall out. + + For Ubuntu 14.04 and later which have version 2.0.12, the changes are + far less invasive and can be categorized as code-hardening. A + substantial portion of changes are are for other distributions. + + -- + [ORIGINAL REPORT] + As we talked, here is the patches we need pick up below change to 12.04, and this request goes urgent for us beucase it's impacting customers. Updates in 2.0.12 Support page blob for status blob https://github.com/Azure/WALinuxAgent/commit/8e506f9696e174fa79b5384af23fed35848d636e Fix extension status on disable success https://github.com/Azure/WALinuxAgent/commit/b655adb4b26ef1723c409fa60ac6696de875853e Update in 2.0.13(all commits based on 2.0.12 based on below branch) https://github.com/Azure/WALinuxAgent/tree/backport [Impact without picking up these fixes] Updates in 2.0.12 - Customer could not get extension status when using D-series VM with ubuntu 12.04 Updates in 2.0.13 - VM with ubuntu 12.04 will get http 410 error, and then WALA service will get crashed in a high failure rate from one of below situations: -Large size VM -All VMS with new Azure CRP -- 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/1449369 Title: [SRU] Update WALinuxAgent to 2.0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1449369/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Patch added: vivid.debdiff https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+attachment/4423974/+files/vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Patch added: trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+attachment/4423971/+files/trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1470580] Re: unprivileged lxc containers fails with custom bridge
Indeed, on every error path lxc_user_nic should print an error message to stderr, but that doesn't end up in the log. If you simply do lxc-start -n container_name -F What do you see? On one failure case I see Quota reached, for instance. When I copy/paste your network config excerpt, it does work for me. Is it possible that x does not have an allocation in /etc/lxc/lxc- usernet for lxcbr0, but the configuration file still has 'lxc.include = /etc/lxc/default.conf' ? Please show the full container config and the full /etc/lxc/lxc-usernet (obfuscated if need be, but then please with annotations so we can be certain). ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+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 1377973] Re: lxc-destroy/lxc-stop gets stuck
[Expired for lxc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxc (Ubuntu) Status: Incomplete = Expired -- 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/1377973 Title: lxc-destroy/lxc-stop gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+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 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
Ok, so this is due to your /etc/libvirt/hooks/qemu script not handling 'reconnect' and exiting with an error. When the hook script exits with an error, the existing vm is terminated. (The error is in your libvirtd.log) So adding a 'exit 0' when called with 'reconnect' will solve this for you. I'm going to mark this bug invalid. If you feel that there is still a real bug, please comment here so we can revisit. ** Changed in: libvirt (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+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 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
I verified the fix works for vivid (2.02~beta2-22ubuntu1.1), trusty (2.02~beta2-9ubuntu1.3) and precise (1.99-21ubuntu3.18). ** 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 the bug report. https://bugs.launchpad.net/bugs/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 335526] Re: suspend/resume broken with ATI HD3650 Asus F8VA
Maybe the same like this here: #1471304 ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/335526 Title: suspend/resume broken with ATI HD3650 Asus F8VA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/335526/+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
Steps to reproduce. 1) install fresh copy of Vivid 2) apt-get -yqq install mysql-server libmysqlclient-dev 3) reboot + system hangs forever (because mysql can't seem to be stopped in all cases by systemd) 4) In another shell - mysqladmin shutdown - allows reboot continues 5) Also - service mysql stop - hangs forever, so only way to consistently stop mysql is via - mysqladmin shutdown This situation only occurs after several mysql restarts + this situation seems to occur on every Vivid install I've done. Down leveling to Utopic is how I've had to fix this. -- 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/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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
The attachment trusty.debdiff seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
After some discussion with Clint on IRC last night, I've uploaded 0.5.1 to vivid-proposed for the SRU team to review. ** Changed in: python-ironicclient (Ubuntu Vivid) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Also affects: neutron (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1471022/+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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
** Description changed: - The nova ironic driver in Kilo was updated to use a new parameter in - ironicclient, configdrive, which was added in v0.4.0 of python- - ironicclient + [Impact] + Users of OpenStack Ironic are not able to boot physical machines using the Nova/Ironic integration; this is due to a misconfigured minimum version requirement upstream for OpenStack Kilo. + + [Test Case] + See original bug report + + [Regression Potential] + Minimal; recommendation from upstream developers to move to 0.5.1 for Kilo compatibility. + + [Original Bug Report] + The nova ironic driver in Kilo was updated to use a new parameter in ironicclient, configdrive, which was added in v0.4.0 of python-ironicclient Test case #. Install kilo nova and kilo ironic #. Configure nova to use ironic virt #. nova boot instance #. Observe failure in nova-compute log showing incorrect configdrive parameter being used. #. update ironicclient to =0.4.1 #. restart nova-compute #. nova boot again #. instance should boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
** Tags added: ironic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
** Description changed: This issue appears to be a consequence of https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572 where we added a 'wait-for-state running' to the nova-compute upstart so as to ensure that neutron-ovs-cleanup has finished before nova-compute starts. I have started to spot, however, that on some hosts (metal only) there - is now a race between the two whereby nova-compute fails to start or - boot/reboot with the following in /var/log/upstart/nova-compute.log: + is now a race between the two whereby nova-compute sometimes fails to + start or boot/reboot with the following in /var/log/upstart/nova- + compute.log: ... libvirt-bin stop/waiting wait-for-state stop/waiting neutron-ovs-cleanup start/pre-start, process 3084 start: Job failed to start If I manually restart nova-compute all is fine. So this looks like a race between nova-compute's wait-for-state and neutron-ovs-cleanup's pre-start - start/running. ** Description changed: This issue appears to be a consequence of https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1420572 where we added a 'wait-for-state running' to the nova-compute upstart so as to ensure that neutron-ovs-cleanup has finished before nova-compute starts. I have started to spot, however, that on some hosts (metal only) there is now a race between the two whereby nova-compute sometimes fails to - start or boot/reboot with the following in /var/log/upstart/nova- + start on system boot/reboot with the following in /var/log/upstart/nova- compute.log: ... libvirt-bin stop/waiting wait-for-state stop/waiting neutron-ovs-cleanup start/pre-start, process 3084 start: Job failed to start If I manually restart nova-compute all is fine. So this looks like a race between nova-compute's wait-for-state and neutron-ovs-cleanup's pre-start - start/running. ** Changed in: neutron (Ubuntu Trusty) Importance: Undecided = High ** Changed in: neutron (Ubuntu Utopic) Importance: Undecided = High ** Changed in: neutron (Ubuntu Vivid) Importance: Undecided = High ** Changed in: neutron (Ubuntu) Status: New = In Progress ** Changed in: neutron (Ubuntu) Assignee: (unassigned) = Edward Hope-Morley (hopem) -- 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/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1471022/+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 1471110] Re: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1471110 Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1471110/+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 1471110] [NEW] package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: accident d'installation récurrent n'empéchant pas a ce jour le bon fonctionnement. Courage et merci. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: setserial 2.17-48ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 Date: Fri Jul 3 08:35:33 2015 DuplicateSignature: package:setserial:2.17-48ubuntu0.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: setserial Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-04-26 (67 days ago) modified.conffile..etc.init.d.etc.setserial: [deleted] modified.conffile..etc.init.d.setserial: [deleted] ** Affects: setserial (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1471110 Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1471110/+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 1267429] Re: Don't slugify() None names (Docker images may have empty names)
** Changed in: python-novaclient (Ubuntu) Status: Fix Committed = Fix Released -- 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/1267429 Title: Don't slugify() None names (Docker images may have empty names) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1267429/+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 1376316] Re: nova absolute-limits floating ip count is incorrect
It looks like nova is only accounting for floating ip's its directly managing (nova-network) rather than those being managed by neutron as in this deployment. Marking 'Confirmed' - I see the same thing on an icehouse deployment; I suspect this is in nova, not the client. ** Changed in: python-novaclient (Ubuntu) Status: New = Confirmed -- 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/1376316 Title: nova absolute-limits floating ip count is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1376316/+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 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1471110] Re: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu, since you appear to have deleted /etc/init.d/setserial which is causing your problem. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: setserial (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1471110 Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1471110/+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 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
Hello Robie, or anyone else affected, Accepted grub2-signed into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.38.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: grub2-signed (Ubuntu Utopic) Status: New = Fix Committed ** Changed in: grub2-signed (Ubuntu Vivid) Status: New = Fix Committed -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1443735] Please test proposed package
Hello Robie, or anyone else affected, Accepted grub2-signed into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.46.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1437398] Re: package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: bacula (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1437398 Title: package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1437398/+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 1437398] Re: package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
From log: Configurando bacula-director-mysql (5.2.6+dfsg-9.1ubuntu4) ... dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version granting access to database bacula for bacula@localhost: success. verifying access for bacula@localhost: success. creating database bacula: success. verifying database bacula exists: success. populating database via sql... done. dbconfig-common: flushing administrative password Creating config file /etc/default/bacula-dir with new version grep: /etc/bacula/bacula-dir.conf: Arquivo ou diretório não encontrado Processing configuration...sed: -e expressão #4, caractere 33: Opção desconhecida para o comando `s' (s///?) dpkg: erro ao processar o pacote bacula-director-mysql (--configure): sub-processo script post-installation instalado retornou estado de saída de erro 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1437398 Title: package bacula-director-mysql 5.2.6+dfsg-9.1ubuntu4 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1437398/+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 1470997] Re: dhclient tries to send request over non-existent interface, floods syslog
Thank you for taking the time to report this bug and helping to make Ubuntu better. I presume you're using Network Manager to manage the connection to your phone over Bluetooth? Assuming this is so, I think this needs to be looked at from the perspective of Network Manager in the first instance. ** Package changed: dhcp3 (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/1470997 Title: dhclient tries to send request over non-existent interface, floods syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1470997/+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 1443735] Please test proposed package
Hello Robie, or anyone else affected, Accepted grub2-signed into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.34.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
Hello Robie, or anyone else affected, Accepted grub2-signed into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.9~ubuntu12.04.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: grub2-signed (Ubuntu) Status: New = Fix Released ** Changed in: grub2-signed (Ubuntu Precise) Status: New = Fix Committed ** Changed in: grub2-signed (Ubuntu Trusty) Status: New = Fix Committed -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
** Branch linked: lp:ubuntu/precise-proposed/grub2-signed ** Branch linked: lp:ubuntu/trusty-proposed/grub2-signed -- 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/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+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 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup
So, this is possibly a result of neutron-ovs-cleaunp failing to start at the time nova-compute does the wait-for-state (and implicitly tries to start neutron-ovs-cleanup) due to the fact that openvswitch is not ready to start at that very moment. I am going to attempt to resolve this by making the nova-compute wait-for-state logic more accommodating of the fact that neutron-ovs-cleanup may not be ready to start at the time of the check. ** Package changed: neutron (Ubuntu) = nova (Ubuntu) -- 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/1471022 Title: [SRU] race between nova-compute and neutron-ovs-cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1471022/+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 1319145] Re: cannot use openstack python client libraries from python3
These have started to trickle through - keystone, glance and cinder are all py3 enabled now. ** Changed in: python-keystoneclient (Ubuntu) Status: Confirmed = Fix Released ** Changed in: python-cinderclient (Ubuntu) Status: Confirmed = Fix Released ** Changed in: python-glanceclient (Ubuntu) Status: Confirmed = Fix Released -- 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
