← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1338735] Re: Live-migration with volumes creates orphan access records

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

** Changed in: nova
     Assignee: Pushkar Umaranikar (pushkar-umaranikar) => (unassigned)

-- 
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/1338735

Title:
  Live-migration with volumes creates orphan access records

Status in Cinder:
  Invalid
Status in OpenStack Compute (nova):
  Expired

Bug description:
  When live migration is performed on instances with volume attached,
  nova sends two initiator commands and one terminate connection. This
  causes orphan access records in some storage arrays ( tested with Dell
  EqualLogic Driver).

  Steps to reproduce:
  1. Have one controller and two compute node setup. Setup cinder volume on iscsi or a storage array.
  2. Create an instance
  3. Create a volume and attach it to the instance
  4. Check the location of the instance ( computenode1 or 2)
  nova instance1 show
  4. Perform live migration of the instance and move it to the second compute node
  nova live-migration instance1 computenode2
  5. Check the cinder api log. c-api
  There will be two os-initialize_connection and one os-terminate-connection. There should only be one set of initialize and terminate connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1338735/+subscriptions


References