| 2015-07-16 19:54:10 |
Anthony Lee |
bug |
|
|
added bug |
| 2015-07-16 19:54:42 |
Anthony Lee |
nova: assignee |
|
Anthony Lee (anthony-mic-lee) |
|
| 2015-07-16 19:55:40 |
Anthony Lee |
description |
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 dangling on the source as the BDM has overridden the connection info with that of the destination.
Code section where this problem is occuring:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6036
At line 6038 the potentially wrong connection info will be passed to _disconnect_volume which then ends up not finding the proper LUNs to remove (and potentially removes the LUNs for a different volume instead).
By adding debug logging after line 6036 and then compare that to the connection info of the source host (by making a call to Cinder's initialize_connection API) you can see that the connection info does not match:
http://paste.openstack.org/show/TjBHyPhidRuLlrxuGktz/
Version of nova being used:
commit 35375133398d862a61334783c1e7a90b95f34cdb
Merge: 83623dd b2c5542
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jul 16 02:01:05 2015 +0000
Merge "Port crypto to Python 3" |
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 dangling on the source as the BDM has overridden the connection info with that of the destination.
Code section where this problem is occuring:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6036
At line 6038 the potentially wrong connection info will be passed to _disconnect_volume which then ends up not finding the proper LUNs to remove (and potentially removes the LUNs for a different volume instead).
By adding debug logging after line 6036 and then comparing that to the connection info of the source host (by making a call to Cinder's initialize_connection API) you can see that the connection info does not match:
http://paste.openstack.org/show/TjBHyPhidRuLlrxuGktz/
Version of nova being used:
commit 35375133398d862a61334783c1e7a90b95f34cdb
Merge: 83623dd b2c5542
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jul 16 02:01:05 2015 +0000
Merge "Port crypto to Python 3" |
|
| 2015-07-16 20:18:14 |
OpenStack Infra |
nova: status |
New |
In Progress |
|
| 2015-07-17 07:42:18 |
Pawel Koniszewski |
tags |
live-migration |
live-migrate |
|
| 2015-08-07 09:57:39 |
Sahid Orentino |
tags |
live-migrate |
kilo-backport-potential live-migrate |
|
| 2015-08-10 11:30:18 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2015-08-19 00:44:23 |
OpenStack Infra |
tags |
kilo-backport-potential live-migrate |
in-stable-kilo kilo-backport-potential live-migrate |
|
| 2015-09-03 11:51:40 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2015-09-03 11:51:40 |
Thierry Carrez |
nova: milestone |
|
liberty-3 |
|
| 2015-09-28 14:57:24 |
Matt Riedemann |
tags |
in-stable-kilo kilo-backport-potential live-migrate |
in-stable-kilo live-migrate |
|
| 2015-09-28 19:20:04 |
OpenStack Infra |
tags |
in-stable-kilo live-migrate |
in-stable-juno in-stable-kilo live-migrate |
|
| 2015-10-11 13:27:09 |
Chuck Short |
nominated for series |
|
nova/kilo |
|
| 2015-10-11 13:27:09 |
Chuck Short |
bug task added |
|
nova/kilo |
|
| 2015-10-11 13:27:20 |
Chuck Short |
nova/kilo: status |
New |
Fix Committed |
|
| 2015-10-11 13:27:26 |
Chuck Short |
nova/kilo: milestone |
|
2015.1.2 |
|
| 2015-10-13 18:22:31 |
Chuck Short |
nova/kilo: status |
Fix Committed |
Fix Released |
|
| 2015-10-15 09:02:13 |
Thierry Carrez |
nova: milestone |
liberty-3 |
12.0.0 |
|
| 2015-11-14 10:36:09 |
Alan Pevec |
nominated for series |
|
nova/juno |
|
| 2015-11-14 10:36:10 |
Alan Pevec |
bug task added |
|
nova/juno |
|
| 2015-11-14 15:10:01 |
Alan Pevec |
nova/juno: status |
New |
Fix Committed |
|
| 2015-11-14 15:10:01 |
Alan Pevec |
nova/juno: milestone |
|
2014.2.4 |
|
| 2015-11-19 21:49:13 |
Alan Pevec |
nova/juno: status |
Fix Committed |
Fix Released |
|
| 2016-01-21 20:31:14 |
Dave Walker |
nova/kilo: status |
Fix Released |
Fix Committed |
|
| 2016-01-21 20:31:14 |
Dave Walker |
nova/kilo: milestone |
2015.1.2 |
2015.1.3 |
|
| 2016-01-21 23:19:31 |
Dave Walker |
nova/kilo: status |
Fix Committed |
Fix Released |
|
| 2016-05-17 15:10:36 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-server-dev/nova/icehouse |
|
| 2016-05-18 09:43:03 |
Martin Pitt |
bug task added |
|
nova (Ubuntu) |
|
| 2016-05-18 09:43:32 |
Martin Pitt |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-05-18 09:43:32 |
Martin Pitt |
bug task added |
|
nova (Ubuntu Trusty) |
|
| 2016-05-24 21:40:22 |
Martin Pitt |
nova (Ubuntu): status |
New |
Fix Released |
|
| 2016-05-24 21:42:10 |
Martin Pitt |
nova (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2016-05-24 21:42:14 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-05-24 21:42:17 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-05-24 21:42:21 |
Martin Pitt |
tags |
in-stable-juno in-stable-kilo live-migrate |
in-stable-juno in-stable-kilo live-migrate verification-needed |
|
| 2016-07-01 23:38:40 |
Billy Olsen |
description |
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 dangling on the source as the BDM has overridden the connection info with that of the destination.
Code section where this problem is occuring:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6036
At line 6038 the potentially wrong connection info will be passed to _disconnect_volume which then ends up not finding the proper LUNs to remove (and potentially removes the LUNs for a different volume instead).
By adding debug logging after line 6036 and then comparing that to the connection info of the source host (by making a call to Cinder's initialize_connection API) you can see that the connection info does not match:
http://paste.openstack.org/show/TjBHyPhidRuLlrxuGktz/
Version of nova being used:
commit 35375133398d862a61334783c1e7a90b95f34cdb
Merge: 83623dd b2c5542
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jul 16 02:01:05 2015 +0000
Merge "Port crypto to Python 3" |
[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 dangling on the source as the BDM has overridden the connection info with that of the destination.
Code section where this problem is occuring:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6036
At line 6038 the potentially wrong connection info will be passed to _disconnect_volume which then ends up not finding the proper LUNs to remove (and potentially removes the LUNs for a different volume instead).
By adding debug logging after line 6036 and then comparing that to the connection info of the source host (by making a call to Cinder's initialize_connection API) you can see that the connection info does not match:
http://paste.openstack.org/show/TjBHyPhidRuLlrxuGktz/
Version of nova being used:
commit 35375133398d862a61334783c1e7a90b95f34cdb
Merge: 83623dd b2c5542
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jul 16 02:01:05 2015 +0000
Merge "Port crypto to Python 3"
[Test Case]
Live migrate an instance which is connected to a volume through multi-path in which the source and target connection information is not the same. Verify that the correct device/LUN is removed (instead of wrong one).
[Regression Potential]
The regression potential is small as it has run in newer versions of nova for awhile now (since Juno, the release immediately following Icehouse). If a regression were to occur it would likely prevent a live migration from completing (failing in the post processing), leaving the instance in an error state. However, it should be migrated to the target hypervisor with access to the LUN so it would require manual cleanup of the lun at the source hypervisor and a reset of the instance state to active. |
|
| 2016-07-01 23:38:54 |
Billy Olsen |
tags |
in-stable-juno in-stable-kilo live-migrate verification-needed |
in-stable-juno in-stable-kilo live-migrate verification-done |
|
| 2016-07-04 09:57:56 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-07-04 09:59:50 |
Launchpad Janitor |
nova (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
