yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16968
[Bug 1338735] [NEW] Live-migration with volumes creates orphan access records
Public bug reported:
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
** Affects: cinder
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Tags: cinder live-migration nova
** Description changed:
When live migration is performed on instances with volume attached, nova
- sends two initiator commands and one ter5.minate connection. This causes
+ 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.
+ 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
+ 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
** Also affects: cinder
Importance: Undecided
Status: New
--
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:
New
Status in OpenStack Compute (Nova):
New
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
Follow ups
References