*** 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
*** 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
*** 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
*** 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
*** 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
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
** 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:
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
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.
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
** 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.
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
--
** 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
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
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
**
** 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
+
** 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.
** 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.
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
[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.
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 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
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
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
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
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,
** 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
** 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
** 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
** 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
** 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
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
** 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
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:
** 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
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
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
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
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
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
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.
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
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.
** 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:
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
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:
46 matches
Mail list logo
