** Changed in: openstack-ansible/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with skb_warn_bad_of
** Changed in: openstack-ansible/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with skb_warn_bad_off
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
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
** Changed in: openvswitch (Ubuntu)
Status: Incomplete => New
--
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/1233703
Title:
openvswitch-datapath-dkms fails to build kerne
@james-page We're testing your upstart openvswitch-switch.conf file on
Precise. It's looking good so far. Can this bug be marked as relevant
for Precise too, please? Once it's in Saucy we'd definitely like to see
it backported to Precise.
--
You received this bug notification because you are a me
Public bug reported:
Ubuntu Precise currently ships with dnsmasq 2.59, but due to the issue
reported in https://lists.launchpad.net/openstack/msg11696.html we
require that to be updated in Precise to at least 2.61. I see that
Quantal already has 2.63. Please backport this update for Precise!
** A