** No longer affects: nova
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902276
Title:
libvirtd going into a tight loop causing instances to not transition
to ACTIVE
To manage notifications
What do we want to do with this bug? Ultimately the underlying issue is
with the version of libvirt shipped in Bionic that's outside of our
control. Should we move the bug to the libvirt component and ask the
Ubuntu team if a rebase is even feasible?
** Also affects: libvirt
Importance:
** Changed in: nova/ocata
Status: Fix Committed => Fix Released
** Changed in: nova/pike
Status: Fix Committed => Fix Released
** Changed in: nova/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks Christian,
I'll confirm that we see error from [2] with that PPA shortly.
In the meantime I've removed the device detach retry logic from
OpenStack Nova and now always see two DEVICE_DELETED events raised by
QEMU after a single device_del request from libvirt:
Here's an example from QMP_requests_and_replies_from_libvirtd.log.gz
attached earlier to the bug by Kashyap. We can see two device_del
commands prior to only seeing a single event emitted by QEMU:
http://paste.openstack.org/show/798607/
# zgrep 0x7f768806eaf0
While testing >=v5.0.0 on Fedora 32 I've stumbled across the following
change in QEMU:
https://github.com/qemu/qemu/commit/cce8944cc9efab47d4bf29cfffb3470371c3541b
The change suggests that previously parallel requests to detach a PCIe
device (such as virtio-blk) from QEMU would result in the
> @Christian Yes we can test this in OpenStack CI with PPAs if you
> could provide Bionic based builds.
I'm not sure what I was thinking here but we *can* use Focal based
builds of QEMU in CI now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Christian Yes we can test this in OpenStack CI with PPAs if you could
provide Bionic based builds.
Better yet I could even try to setup a git bisect locally if you have
steps to build from a source tree somewhere?
@James Did you try using OpenStack CI sized hosts (8 vCPUs, 8GB of RAM)
and the
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896617
Title:
Creation of image (or live snapshot) from the existing VM fails if
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864020
Title:
** Changed in: nova
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864020
Title:
libvirt.libvirtError: Requested operation is not valid: format of
Released in 17.0.10.
** Changed in: nova/queens
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809454
Title:
[SRU] nova rbd auth fallback uses cinder
Thanks Corey, Christian, the new build WORKSFORME!
# virsh attach-device test disk.xml
error: Failed to attach device from disk.xml
error: unsupported configuration: luks encryption requires encrypted secrets to
be supported
# add-apt-repository cloud-archive:ocata-proposed
# apt-get update
#
So the issue only appears with the Ocata UCA repo that provides the
2.5.0-3ubuntu5.6~cloud0 build. Why we are installing this in the
OpenStack CI upgrade jobs between Pike and Queens is beyond me but
something we should be able to correct outside of this bug.
Anyway, here are some notes on
Public bug reported:
Currently seeing the following error in OpenStack CI on 16.04 with
Libvirt 2.5.0 provided via the UCA when attempting to create a `luks`
Libvirt secret:
http://logs.openstack.org/50/536350/1/check/legacy-grenade-dsvm-neutron-
multinode-live-
As discussed on the ML in c#25 we are continuing to see this in the
OpenStack CI. I've included some links to some examples below :
http://logs.openstack.org/43/458843/1/check/gate-tempest-dsvm-multinode-live-migration-ubuntu-xenial/747160c/logs/subnode-2/libvirt/qemu/instance-0002.txt.gz
Moving to invalid as this should no longer reproduce against Liberty or
Mitaka after the move os-brick. Please reopen and reassign to os-brick
if this issue persists.
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: nova
Assignee: Jorge Niedbalski (niedbalski) =>
17 matches
Mail list logo
