cloudstack/engine
Harikrishna 12b2e80d82
vmware: Fix fetching chain_info of the volumes. It is used to assume datastore names are in the form of UUIDs but it can be any name. So fetch chain_info based on the datastore name. (#5097)
his PR fixes the problem of not updating the chain info or setting chain info to null after volume migrations.

Problem: While fetching the volume chain info, management server assumes datastore name to be a UUID (this is true only for NFS storages added by CloudStack) but datastore name can be with any name.
Solution: To fetch the volume chain info, use datastore name instead of UUID.

The fix is made in the flow of following API operations

migrateVirtualMachine
migrateVirtualMachineWithVolume
migrateVolume
2021-06-11 20:06:06 +05:30
..
api server: Allow to upgrade service offerings from local <> shared storage pools (#4915) 2021-04-30 11:59:50 +05:30
components-api Merge remote-tracking branch 'origin/4.14' into 4.15 2021-05-14 23:19:06 +05:30
network Updating pom.xml version numbers for release 4.14.2.0-SNAPSHOT 2021-03-02 12:32:27 +05:30
orchestration vmware: Fix fetching chain_info of the volumes. It is used to assume datastore names are in the form of UUIDs but it can be any name. So fetch chain_info based on the datastore name. (#5097) 2021-06-11 20:06:06 +05:30
schema kvm: Check for VLAN or VXLAN in NetworkDaoImpl.listByPhysicalNetworkPvlan (#5074) 2021-06-05 22:25:01 +05:30
service Updating pom.xml version numbers for release 4.14.2.0-SNAPSHOT 2021-03-02 12:32:27 +05:30
storage VMware Datastore Cluster primary storage pool synchronisation (#4871) 2021-05-07 16:30:54 +05:30
pom.xml Updating pom.xml version numbers for release 4.14.2.0-SNAPSHOT 2021-03-02 12:32:27 +05:30