This bug was fixed in the package nova - 2:20.6.1-0ubuntu1~cloud0
---
nova (2:20.6.1-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New stable point release for OpenStack Train (LP: #1935031).
.
nova (2:20.6.0-0ubuntu1~cloud1) bionic-train; urgency=medium
.
*
The changelog entry that triggered the update was included in the latest
point as a result of a build flag including it, this bug has already
been accepted into -updates.
** Changed in: cloud-archive/train
Status: Fix Committed => Fix Released
--
You received this bug notification
This bug was fixed in the package nova - 2:20.6.0-0ubuntu1~cloud1
---
nova (2:20.6.0-0ubuntu1~cloud1) bionic-train; urgency=medium
.
* d/p/restore-migrate-data-vifs(-tests).patch: Cherry-picked from
upstream stable/train to fix live migration of VM's using the single
Marking this fix-released on upstream's Train as a fix was committed on
https://review.opendev.org/c/openstack/nova/+/759533
** Changed in: nova/train
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After installing/upgrading the "train-proposed" packages and restarting
the nova-compute service on the nova-compute nodes it was possible to do
live-migration in the environment.
Updated packages:
nova-api-metadata nova-common nova-compute nova-compute-kvm
nova-compute-libvirt python3-nova
**
I've tested this out using the latest stable/train release from opendev.
My initial tests are allowing me to live migrate back and forth again.
Haven't gotten to every corner case but this looks promising.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reviewed: https://review.opendev.org/c/openstack/nova/+/759533
Committed:
https://opendev.org/openstack/nova/commit/a4e2a6a41239a682c0da553ec5938737d0b85b52
Submitter: "Zuul (22348)"
Branch:stable/train
commit a4e2a6a41239a682c0da553ec5938737d0b85b52
Author: Sean Mooney
Date: Fri Aug 21
** Changed in: cloud-archive/ussuri
Status: New => 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/1888395
Title:
live migration of a vm using the single port binding work flow is
This bug was fixed in the package nova - 2:21.2.0-0ubuntu1
---
nova (2:21.2.0-0ubuntu1) focal; urgency=medium
* New stable point release for OpenStack Ussuri (LP: #1923036).
* d/p/lp1888395-*: Removed after patch landed upstream.
nova (2:21.1.2-0ubuntu2) focal; urgency=medium
The patches for LP:#1888395 were reverted with the ensuing point release
that was picked up in 1923036, so I think the testing of LP:#1923036 can
cover it.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received
** Changed in: nova/ussuri
Status: Fix Committed => 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/1888395
Title:
live migration of a vm using the single port binding work flow
** Changed in: nova/train
Assignee: Billy Olsen (billy-olsen) => sean mooney (sean-k-mooney)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888395
Title:
live migration of a vm using the
I see that this code change already exists in Ubuntu Hirsute, so I'm
setting that task Fix Released.
> rewriting the bug desciption to follow the downstream bug template
could cause confution in some cases so that might be better to keep in a
comment
FWIW, from the Ubuntu SRU team perspective I
Out of curiosity, I just searched through Nova bugs that are fix-
committed or fix-released that also have the 'verification-done' tag
(one of the tags used for SRU processing into older Ubuntu released),
and found that there are a reasonable amount of upstream bugs that are
also used for Ubuntu &
@sean I don't think we have a standard of not re-using upstream bugs for
distro. I've thought about this frequently but up to this point nobody
complained, to me at least, so I've just continued on. I personally like
to re-use the upstream bug since it's nice to have everything in one
place and
by the way i also want to see this backported to train upstream so any
review ectra that ye can provide to make that happen more quickly is
great :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i tought that cannonical did not reuse upstream project bugs for
tracking the change in teh ubuntu cloud archive?
the convention previously was to file a different bug for the cloud
archive that referenced the upstream bug no?
using the same bug for upstream and downstream kind of make it hard
** Description changed:
- it was working in queens but fails in train. nova compute at the target
- aborts with the exception:
+ [Impact]
+
+ Live migration of instances in an environment that uses neutron backends
+ that do not support multiple port bindings will fail with error
+
Corey - they are, and I've been working on them here and there to get
them into shape. The Train version might slightly differ in the
functional tests that are being added, but the actual code change is the
same.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Billy/Xav, Is there any chance these patches are appropriate to land in
upstream stable/train?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888395
Title:
live migration of a vm using the single
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu Groovy)
Status: New =>
21 matches
Mail list logo
