[jira] [Resolved] (CLOUDSTACK-4191) [Object_store_refactor] Uploaded voluem is getting deleted from secondary staging storage after attaching to VM

["Min Chen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Min Chen resolved CLOUDSTACK-4191.
----------------------------------

    Resolution: Fixed
    
> [Object_store_refactor] Uploaded voluem is getting deleted from secondary staging storage after attaching to VM
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4191
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4191
>             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.0
>         Environment: Latest build from ACS 4.2 branch
> Storage: S3 for secondray, NFS for secondary staging and ISCSI for primary storage
> cluster: VMWare
>            Reporter: Sanjeev N
>            Assignee: Min Chen
>             Fix For: 4.2.0
>
>         Attachments: cloud.dmp, management-server.rar
>
>
> Uploaded voluem is getting deleted from secondary staging storage after attaching to VM
> During volume attach process volume gets copied from S3 to secondary staging storage and from there to Primary storage.
> After attach volume is getting deleted from secondary staging storage. But the entries created in volume_store_ref table with store_id pointing to "Secondary staging storage" shows the stat as Ready.
> Either we should not delete the volume from secondary staging storage or should mark the state as Destroyed/Removed.
> Steps to Reproduce:
> ================
> 1.Bring up CS with vmware cluster using S3 for secondray, NFS for secondary staging and ISCSI for primary storage
> 2.Deploy guest vm using default cent os template
> 3.Upload volume using:
> http://10.147.59.126:8096/client/api?command=uploadVolume&format=OVA&name=cent53-upload2&url=http://10.147.28.7/templates/vmware/CentOS5.3-x86_64.ova&zoneid=f4d765fb-82c1-4a1c-b8cd-48c79ca21a34&account=admin&domainid=1
> 4.Attach it to vm created above.
> Attaching management server log file and cloud db.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira