You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/09/27 07:10:05 UTC

[GitHub] [cloudstack] sureshanaparti opened a new issue #5514: Migrate volume across different PowerFlex storage clusters, ignores the disk copy failure (in KVM)

sureshanaparti opened a new issue #5514:
URL: https://github.com/apache/cloudstack/issues/5514


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   Migrate volume across different PowerFlex storage clusters, ignores the disk copy failure (in KVM)
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   
   ~~~
   Volume
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main branch.
   -->
   
   ~~~
   main
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   CloudStack + KVM + (atleast) Two Storage pools from different PowerFlex storage clusters
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Migrate volume across different PowerFlex storage clusters, is performed through the block copy (using 'qemu-img convert' cmd) from source to dest disk. The block copy failure is being ignored, and migration is marked as success. This is leaving behind a blank disk on the target storage pool.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   - Add two (zone-wide) storage pools (say _powerflex1_, _powerflex2_ ) from different PowerFlex storage clusters.
   - Create a volume on the first storage pool (_powerflex1_) and attach to any VM.
   - Migrate volume to the second storage pool (_powerflex2_) . Try to fail the block copy operation ('qemu-img convert' cmd) in the host.
   
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   Volume migration should fail, when the disk copy fails
   
   
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   Volume migration passes, leaving behind a blank disk on the target storage pool.
   
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

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



[GitHub] [cloudstack] nvazquez closed issue #5514: Migrate volume across different PowerFlex storage clusters, ignores the disk copy failure (in KVM)

Posted by GitBox <gi...@apache.org>.
nvazquez closed issue #5514:
URL: https://github.com/apache/cloudstack/issues/5514


   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

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