[ https://issues.apache.org/jira/browse/CLOUDSTACK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek updated CLOUDSTACK-4536: ------------------------------------------- Assignee: edison su > [object_store_refactor] Inconsistency in volume store location on secondary > storage for uploaded and extracted volume > --------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-4536 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4536 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware, Volumes > Affects Versions: 4.2.1 > Environment: git rev-parse HEAD~5 > 1f46bc3fb09aead2cf1744d358fea7adba7df6e1 > Hypervisor: VMWare > Reporter: Sanjeev N > Assignee: edison su > Fix For: 4.3.0 > > > Inconsistency in volume store location on secondary for uploaded and > extracted volume in case of vmware > Volumes are stored in the secondary storage under following two conditions: > 1.Uploaded volume > 2.Extract(Download volume) > In case 1 volume is stored in > <NFS_secondary_storage_path>/volumes/<account-id>/<volume-id>/uuid.ova > In case 2 volume is stored in > <NFS_secondary_storage_path>/volumes/<account-id>/<volume-id>/<uuid>/uuid.ova > Did not see any issues with this approach but the store location is > inconsistent. -- This message was sent by Atlassian JIRA (v6.1#6144)