incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das" <>
Subject Review Request: Fix for CS-15621
Date Fri, 03 Aug 2012 10:04:36 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack, Prachi Damle and Nitin Mehta.


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.


  server/src/com/cloud/storage/ a2ea98d 



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


Koushik Das

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message