Re: [Openstack-operators] mitaka/xenial libvirt issues

his. To confirm: did you also > downgrade libvirt as well or was it all qemu? > > Thanks, > Joe > > On Thu, Nov 23, 2017 at 9:16 AM, Chris Sarginson <csarg...@gmail.com> > wrote: > >> We hit the same issue a while back (I suspect), which we seemed to >> reso

Re: [Openstack-operators] mitaka/xenial libvirt issues

We hit the same issue a while back (I suspect), which we seemed to resolve by pinning QEMU and related packages at the following version (you might need to hunt down the debs manually): 1:2.5+dfsg-5ubuntu10.5 I'm certain there's a launchpad bug for Ubuntu qemu regarding this, but don't have it

Re: [Openstack-operators] Neutron Issues

If you're using openvswitch, with Newton there was a change to the default agent for configuring openvswitch to be the python ryu library, I think it's been mentioned on here recently, so probably worth having a poke through the archives for more information. I'd check your neutron openvswitch

Re: [Openstack-operators] live migration fails and libvirtd(?) lockup after trusty > xenial/mitaka > newton upgrade

Hi Vladimir, The packages are available on launchpad here: https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-5ubuntu10.5/+build/10938755 On Tue, 20 Dec 2016 at 12:49 Vladimir Prokofev wrote: > Using > compute1:~$ dpkg-query -W qemu-system-x86 > qemu-system-x86

Re: [Openstack-operators] Instances failing to launch when rbd backed (ansible Liberty setup)

It seems like it may be an occurrence of this bug, as you look to be using python venvs: https://bugs.launchpad.net/openstack-ansible/+bug/1509837 2016-10-21 12:08:06.242 70661 ERROR nova.compute.manager [instance: 5633d98e-5f79-4c13-8d45-7544069f0e6f] File "*/openstack/venvs/*nova-12.0.