yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #71615
[Bug 1754716] [NEW] Disconnect volume on live migration source fails if initialize_connection doesn't return identical output
Public bug reported:
During live migration we update bdm.connection_info for attached volumes
in pre_live_migration to reflect the new connection on the destination
node. This means that after migration completes we no longer have a
reference to the original connection_info to do the detach on the source
host, so we have to re-fetch it with a second call to
initialize_connection before calling disconnect.
Unfortunately the cinder driver interface does not strictly require that
multiple calls to initialize_connection will return consistent results.
Although they normally do in practice, there is at least one cinder
driver (delliscsi) which doesn't. This results in a failure to
disconnect on the source host post migration.
** Affects: nova
Importance: Undecided
Assignee: Matthew Booth (mbooth-9)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1754716
Title:
Disconnect volume on live migration source fails if
initialize_connection doesn't return identical output
Status in OpenStack Compute (nova):
In Progress
Bug description:
During live migration we update bdm.connection_info for attached
volumes in pre_live_migration to reflect the new connection on the
destination node. This means that after migration completes we no
longer have a reference to the original connection_info to do the
detach on the source host, so we have to re-fetch it with a second
call to initialize_connection before calling disconnect.
Unfortunately the cinder driver interface does not strictly require
that multiple calls to initialize_connection will return consistent
results. Although they normally do in practice, there is at least one
cinder driver (delliscsi) which doesn't. This results in a failure to
disconnect on the source host post migration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1754716/+subscriptions
Follow ups