Devdeep Singh created CLOUDSTACK-7359: -----------------------------------------
Summary: Volume migration between pools times out on cloudstack, but the migration completes on Xenserver Key: CLOUDSTACK-7359 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7359 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Devdeep Singh Assignee: Devdeep Singh Priority: Critical When a volume is live migrated from one storage pool to another, cloudstack sends a migratecommand to the resource. The agent waits for wait*3 seconds for the command to complete. Whereas the resource waits for migratewait seconds for the migration to complete. If volume migration doesn't complete within migratewait interval the operation is cancelled. (wait and migratewait for global configurable parameters). If wait parameter is much less than migratewait; the agent assumes the operation hasn't completed and moves ahead. On the resource side the operation would go ahead and complete at a later point in time. This leads to the volume being moved to a different storage pool, but the location isn't updated on the db. Subsequent operation on the vm/volume like stop start etc. will fail. -- This message was sent by Atlassian JIRA (v6.2#6252)