[GitHub] [cloudstack] borisstoyanov edited a comment on issue #4043: Volume migration

[GitBox <gi...@apache.org>]

borisstoyanov edited a comment on issue #4043:
URL: https://github.com/apache/cloudstack/pull/4043#issuecomment-618484751


   Looks good, I've managed to reproduce your case by having the secondary storage occupied with more than 90% and then migrated a detached volume to an available primary pool. 
   
   Before migration in pool2 
   ```
   [root@SBLabNestedNFS ref-trl-857-k-M7-boris-stoyanov-kvm-pri2]# ll -lahi
   87949354 -rw-r--r--. 1 root root 193K Apr 23 16:39 c2546555-8fc1-4167-b881-15d918072215
   ```
   
   Migrated to pool1, immediately failed with this in management: 
   ```
   2020-04-23 15:46:32,423 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-9:ctx-8531963e job-71) (logid:6ce344d9) Unexpected exception while executing org.apache.cloudstack.api.command.admin.volume.MigrateVolumeCmdByAdmin
   com.cloud.utils.exception.CloudRuntimeException: Resource [StoragePool:1] is unreachable: Migrate volume failed: can't find a nfs (or cifs) image store to satisfy the need for a staging store
   ```
   
   And then file was still available in Cloudstack: 
   ```
   [root@SBLabNestedNFS ref-trl-857-k-M7-boris-stoyanov-kvm-pri2]# ll -lahi
   87949354 -rw-r--r--. 1 root root 193K Apr 23 16:39 c2546555-8fc1-4167-b881-15d918072215
   
   ```
   
   Lets wait for marvin tests to finish overnight and this should be good to go.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org