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

edison su reassigned CLOUDSTACK-4318:
-------------------------------------

    Assignee: edison su
    
> [Object_Store_Refactor] Failed to delete snapshot copied to Staging storage 
> during snapshot creation
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4318
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4318
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: KVM, Snapshot, Storage Controller
>    Affects Versions: 4.2.0
>         Environment: Latest build from ACS 4.2 branch
> Storage:S3 for Secondary, NFS for staging and Local for Primary storage
> Cluster: KVM
>            Reporter: Sanjeev N
>            Assignee: edison su
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Failed to delete snapshot copied to Staging storage during snapshot creation. 
> During snapshot creation process snapshot will be copied to Staging storage 
> and from there to S3. Once the snapshot is backed up to S3 CS tries to delete 
> the snapshot from the staging storage. 
> Steps to Reproduce:
> =================
> 1.Bring up CS with kvm cluster using S3 for Secondary, NFS for staging and 
> Local for Primary storage
> 2. Deploy guest vm with root and data disk
> 3.Take snapshot of the data disk
> Observations:
> ==========
> After snapshot is backed up CS sends deleteCommand  to delete the snapshot 
> from staging storge.
> 2013-08-14 06:11:52,573 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-5:null) Seq 1-1253835537: Processing:  { Ans: , MgmtId: 
> 6615759585382, via: 1, Ver: v1, Flags: 10, 
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"newData":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/13/6d2f2c58-03a4-4406-b738-73ed00c74f6a","id":0}},"result":true,"wait":0}}]
>  }
> 2013-08-14 06:11:52,573 DEBUG [agent.transport.Request] 
> (Job-Executor-22:job-32 = [ 5daad4d3-7a5b-4aff-ace9-d417bee0565e ]) Seq 
> 1-1253835537: Received:  { Ans: , MgmtId: 6615759585382, via: 1, Ver: v1, 
> Flags: 10, { CopyCmdAnswer } }
> 2013-08-14 06:11:52,580 DEBUG [agent.transport.Request] 
> (Job-Executor-22:job-32 = [ 5daad4d3-7a5b-4aff-ace9-d417bee0565e ]) Seq 
> 3-1833173012: Sending  { Cmd , MgmtId: 6615759585382, via: 3, Ver: v1, Flags: 
> 100011, 
> [{"org.apache.cloudstack.storage.command.DeleteCommand":{"data":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/13","volume":{"uuid":"0023a635-b1ca-499d-91b3-ddca2a4fa84d","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"a01b8b56-4987-4843-be07-e48f1c584498","id":1,"poolType":"Filesystem","host":"10.147.40.14","path":"/var/lib/libvirt/images","port":0}},"name":"DATA-8","size":5368709120,"path":"8a8b01a1-898a-498f-9b13-ca8b873586c5","volumeId":13,"vmName":"i-2-8-VM","accountId":2,"format":"QCOW2","id":13,"hypervisorType":"KVM"},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/sanjeev/sec_kvm_os","_role":"ImageCache"}},"vmName":"i-2-8-VM","name":"HourlyDaily_DATA-8_20130814101143","hypervisorType":"KVM","id":7}},"wait":0}}]
>  }
> 2013-08-14 06:11:52,665 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-7:null) Seq 3-1833173012: Processing:  { Ans: , MgmtId: 
> 6615759585382, via: 3, Ver: v1, Flags: 10, 
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"failed to delete 
> snapshot 
> /mnt/SecStorage/0049354e-1f59-33c2-8bb6-760c9b2fa6ad/snapshots/2/*13* , 
> err=Failed to delete file 
> /mnt/SecStorage/0049354e-1f59-33c2-8bb6-760c9b2fa6ad/snapshots/2/*13*, 
> err=rm: cannot remove 
> `/mnt/SecStorage/0049354e-1f59-33c2-8bb6-760c9b2fa6ad/snapshots/2/13': Is a 
> directory","wait":0}}] }

--
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

Reply via email to