commit 8b649aa86fb26e998d66e75e5cebfd19c396942d
Author: Anthony Lee <email address hidden>
Date: Thu Jul 16 13:02:00 2015 -0700
Fix live-migrations usage of the wrong connector information
During the post_live_migration step for the Nova libvirt driver
an incorrect assumption is being made about the connector
information being sent to _disconnect_volume. It is assumed that
the connection information on the source and destination is the
same but that is not always the case. The BDM, where the
connector information is being retrieved from only contains the
connection information for the destination. This will not work
when trying to disconnect volumes from the source during live
migration as the properties such as the target_lun and
initiator_target_map could be different. This ends up leaving
behind dangling LUNs and possibly removing the incorrect
volume's LUNs.
The solution proposed here utilizes the connection_info that
can be retrieved for a host from Cinder's initialize_connection
API. This connection information contains the correct data for
the source host and allows volume LUNs to be removed properly.
Reviewed: https:/ /review. openstack. org/202770 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=8b649aa86fb 26e998d66e75e5c ebfd19c396942d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8b649aa86fb26e9 98d66e75e5cebfd 19c396942d
Author: Anthony Lee <email address hidden>
Date: Thu Jul 16 13:02:00 2015 -0700
Fix live-migrations usage of the wrong connector information
During the post_live_migration step for the Nova libvirt driver target_ map could be different. This ends up leaving
an incorrect assumption is being made about the connector
information being sent to _disconnect_volume. It is assumed that
the connection information on the source and destination is the
same but that is not always the case. The BDM, where the
connector information is being retrieved from only contains the
connection information for the destination. This will not work
when trying to disconnect volumes from the source during live
migration as the properties such as the target_lun and
initiator_
behind dangling LUNs and possibly removing the incorrect
volume's LUNs.
The solution proposed here utilizes the connection_info that connection
can be retrieved for a host from Cinder's initialize_
API. This connection information contains the correct data for
the source host and allows volume LUNs to be removed properly.
Change-Id: I3dfb75eb58dfbc 66b218bcee473af 4c2ac282eb6
Closes-Bug: #1475411
Closes-Bug: #1288039
Closes-Bug: #1423772