Fix for CS-15621
Review Request #6337 - Created Aug. 3, 2012 and submitted
Using migrateVolumes method which does not perform input validation. Some input validation in the migrateVolume method prevented migration of volume in READY state. Also using volume disk offering to check if it is a local or shared one.
Verified on XS 6.0.2 Test scenario - Created 2 shared primary storage pools - Created data volume using shared disk offering - Attached it to a running VM (created in one storage pool) - Detached it (now it is in READY state) - Created a new VM in stopped state (using deployVirtualMachine API with startVm=false) - Attached the data volume to this new VM - Started new VM (migrated volume scenario got hit when the planner assigned the other shared pool)
Review request changed
Updated (Aug. 12, 2012, 1:28 p.m.)
- changed from pending to submitted