borisstoyanov opened a new issue #4400:
URL: https://github.com/apache/cloudstack/issues/4400
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master 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
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VMware migration, API
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master
branch.
-->
~~~
4.14
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
VMware
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When executing the api agains attached volume we observe that none of the
pools is marked suitable, a little investigation was done suspecting the
following change:
https://github.com/shapeblue/cloudstack/blob/ovfprops-and-vsphere-adv-together/server/src/main/java/com/cloud/server/ManagementServerImpl.java#L156
```
//This is an override mechanism so we can list the possible local
storage pools that a volume in a shared pool might be able to be migrated to
diskProfile.setUseLocalStorage(true);
```
Before searching for the suitable storage pools, volume is marked as using
local storage just to also find any local storage pools to which volume can be
migrated along with the shared storage pools.
But this is causing regression for zone wide storage pools, while zone wide
storage pool allocator searches for any zone wide storage pools the entrance
check is
`if (dskCh.useLocalStorage()) { return null;}
`which causing zone wide storage pool allocator returning nothing and at the
end findStoragePoolsForMigration API shows all zone wide storage pools are “not
suitable“.
Below is the screenshot of a volume which is not associated with any storage
policy but still showing “vvol5-zone“ as “not suitable“.
----------------------------------------------------------------
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:
[email protected]
