tsinik-dw opened a new issue #5915:
URL: https://github.com/apache/cloudstack/issues/5915
<!--
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.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
* Improvement Request
* Enhancement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.16.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
ACS 4.16.0
1 Zone
Cluster A: Two Xenserver 7.0 hosts
Cluster B: Two XCP-NG 8.2 hosts
Each Cluster has each own NFS primary storage (non-managed storage)
There is a Zone-wide Solidfire Storage (managed storage)
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
VM-A1, on Cluster A, has 1 ROOT disk and 1 DATA disk. Both disks on NFS
Primary storage
VM-A2, on Cluster A, has 1 ROOT disk and 1 DATA disk. Both disks on
Solifire storage
VM-B1, on Cluster B, has 1 ROOT disk and 1 DATA disk. Both disks on NFS
Primary storage
VM-B2, on Cluster B, has 1 ROOT disk and 1 DATA disk. Both disks on
Solifire storage
##### SUMMARY
<!-- Explain the problem/feature briefly -->
We want to migrate VM DATA volumes between NFS primary storage (non-managed
storage) and Solidfire storage (managed storage), both ways.
1. Trying to migrate VM-A1, VM-B1 Volumes from non-managed --> Managed
(TRIED WITH VMs IN RUNNING AND STOPPED STATE, SAME RESULT)
The UI does not offer any available storage choice and we get the
following message:
~~~
No primary storage pools available for migration
~~~
2. Trying to migrate VM-A2, VM-B2 Volumes from Managed --> Unmanaged: (TRIED
WITH VMs IN RUNNING AND STOPPED STATE, SAME RESULT)
We get the following message:
~~~
Migrating volume failed
Resource [StoragePool:1] is unreachable: Migrate volume failed:
com.cloud.utils.exception.CloudRuntimeException:
Migration operation failed in
'StorageSystemDataMotionStrategy.handleVolumeMigrationFromManagedStorageToNonManagedStorage':
Currently, only the KVM hypervisor type is supported for the migration
of a volume from managed storage to non-managed storage.>
~~~
It turns out that this feature is only supported on KVM
##### 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.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create VM1 with DATA volume on Solidfire storage
2. Create VM2 with DATA volume on NFS primary storage
3. Try to migrate VM1 DATA volume from Solidfire to NFS Storage
4. Try to migrate VM2 DATA volume from NFS to Solidfire Storage
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
DATA volume should be migrated
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
We want to migrate VM DATA volumes between NFS primary storage (non-managed
storage) and Solidfire storage (managed storage), both ways.
1. Trying to migrate VM-A1, VM-B1 Volumes from non-managed --> Managed
(TRIED WITH VMs IN RUNNING AND STOPPED STATE, SAME RESULT)
The UI does not offer any choice and we get the following message:
No primary storage pools available for migration
1. Trying to migrate VM-A2, VM-B2 Volumes from Managed --> Unmanaged: (TRIED
WITH VMs IN RUNNING AND STOPPED STATE, SAME RESULT)
We get the following message:
Migrating volume failed
Resource [StoragePool:1] is unreachable: Migrate volume failed:
com.cloud.utils.exception.CloudRuntimeException:
Migration operation failed in
'StorageSystemDataMotionStrategy.handleVolumeMigrationFromManagedStorageToNonManagedStorage':
Currently, only the KVM hypervisor type is supported for the migration
of a volume from managed storage to non-managed storage.>
It turns out that this feature is only supported on KVM
~~~
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
