Verified nova update for pike using tempest live migration tests and
some manual exercising of live-migration including block-migration with
attached storage volumes from cinder (yikes!).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package nova - 2:16.0.0-0ubuntu2~cloud0
---
nova (2:16.0.0-0ubuntu2~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
nova (2:16.0.0-0ubuntu2) artful; urgency=medium
.
* d/p/qemu-2.10-compat.patch: Compatibility patc
Fix promoted to pike-proposed.
** Changed in: cloud-archive/pike
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/1718133
Title:
Live block migration in Pik
This bug was fixed in the package nova - 2:16.0.0-0ubuntu2
---
nova (2:16.0.0-0ubuntu2) artful; urgency=medium
* d/p/qemu-2.10-compat.patch: Compatibility patch to resolve issues
with qemu-img info calls on running instances, which blocks live
migration of instances among ot
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live block migration in Pike fails due to qemu-img
To manage notifications about this bug go to:
https://bugs.launc
** Patch added: "qemu-2.10-compat.patch"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1718133/+attachment/4953631/+files/qemu-2.10-compat.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: nova (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: nova (Ubuntu Artful)
Assignee: (unassigned) => James Page (james-page)
** Changed in: cloud-archive/pike
Status: Triaged => In Progress
** Changed in: cloud-archive/pike
Assignee: (unassigne
I've uploaded test packages to:
https://launchpad.net/~james-page/+archive/ubuntu/pike
The patch this includes will only work with qemu 2.10 as found in artful
and the Pike UCA; will need todo a larger patch for submission to Nova
to deal with multiple versions.
--
You received this bug notif
Nova/devstack bug 1718295
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live block migration in Pike fails due to qemu-img
To manage notifications about this bug go to:
https://bugs.
Yepp, it works!
qemu-img info --force-share disk
It is easy to add this into Nova. Just need to care of older qemu-img
versions somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Marking qemu task as invalid - this is really a new feature that nova
needs to deal with.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Importance: Undecid
While not appeared on the Mailing List Archive as a link I have the
reply.
TL;DR: The --no-lock option was later revised into --force-share
So you'd need to revise the calling code to:
$ qemu-img info --force-share ...
If you want/need to probe for lock features to know when to add that
flag (ot
I sent a mail upstream asking for the outcome of that old effort and describing
our current issue with it.
Will add a link to Mail-Archive once I have it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This patch set was never accepted that way, but yeah reviving that might
be an option to work around this. Also this was long ago, but the lock
rewrite/enablement happened only recently so a totally new approach
might be needed (or is present without us knowing).
We might ping qemu-devel about tha
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live
Seems there was a patchset submitted, but I don't see --no-lock or -L options
in qemu-img:
https://lists.gnu.org/archive/html/qemu-block/2016-04/msg00349.html
If it would be there, then nova could call qemu-img --no-lock ...
--
You received this bug notification because you are a member of Ubun
Pike UCA is in sync with Artful versions; I'm working to reproduce so we
can debug further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live block migration in Pike fails due to qem
Maybe this is the problem (from Qemu 2.10 changelog):
- Image locking is added and enabled by default. Multiple QEMU processes
cannot write to the same image as long as the host supports OFD or posix
locking, unless options are specified otherwise.
But 'qemu-img info' should not require a write l
@James, I found and fixed some of these issues, just look at "fixed in RC" on
[1].
Since then all migrations I had worked, we need to find what is special in this
case.
When reproducing watch out for:
- do you have the latest qemu /libvirt matching artful or is something left to
be promoted to
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live block migration in Pike fails due to qemu-img
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live
21 matches
Mail list logo
