[Bug 1475411] Re: During post_live_migration the nova libvirt driver assumes that the destination connection info is the same as the source, which is not always true

2016-07-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nova - 1:2014.1.5-0ubuntu1.5 --- nova (1:2014.1.5-0ubuntu1.5) trusty; urgency=medium * Fix live migration usage of the wrong connector (LP: #1475411) - d/p/Fix-live-migrations-usage-of-the-wrong-connector-inf.patch * Fix wrong used ProcessExec

[Bug 1475411] Re: During post_live_migration the nova libvirt driver assumes that the destination connection info is the same as the source, which is not always true

2016-07-01 Thread Billy Olsen
** Description changed: + [Impact] + The post_live_migration step for Nova libvirt driver is currently making a bad assumption about the source and destination connector information. The destination connection info may be different from the source which ends up causing LUNs to be left dan

[Bug 1475411] Re: During post_live_migration the nova libvirt driver assumes that the destination connection info is the same as the source, which is not always true

2016-05-24 Thread Martin Pitt
OK. Please always set correct task states, to avoid stalling SRUs due to that. ** Changed in: nova (Ubuntu) Status: New => Fix Released ** Changed in: nova (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification becaus

[Bug 1475411] Re: During post_live_migration the nova libvirt driver assumes that the destination connection info is the same as the source, which is not always true

2016-05-18 Thread Corey Bryant
Hi Martin. This was fixed upstream in nova for OpenStack Juno which mapped to Utopic. So it is already fixed in Utopic and all releases after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475411

[Bug 1475411] Re: During post_live_migration the nova libvirt driver assumes that the destination connection info is the same as the source, which is not always true

2016-05-18 Thread Martin Pitt
There is an SRU waiting in the trusty-proposed queue for this. Please clarify in which Ubuntu release(s) this is already fixed, or upload the fix to yakkety, so that the trusty SRU can proceed. ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubun