You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sailaja Mada (JIRA)" <ji...@apache.org> on 2013/10/21 12:28:43 UTC

[jira] [Commented] (CLOUDSTACK-4907) [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800526#comment-13800526 ] 

Sailaja Mada commented on CLOUDSTACK-4907:
------------------------------------------

2013-10-21 15:47:10,919 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) ===END===  10.144.6.15 -- GET  command=createSnapshot&volumeid=3f5a1d55-a0e3-4580-b0f7-1c3f13ae1f7b&response=json&sessionkey=%2FIZ1HaelGzG022fKFel6n0xfjTo%3D&_=1382350935875
2013-10-21 15:47:10,922 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-26:job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ]) Executing org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ]
2013-10-21 15:47:10,931 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-26:job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ]) Access to Acct[88304141-9e0d-4ed9-9e47-b650c013af9f-user1] granted to Acct[88304141-9e0d-4ed9-9e47-b650c013af9f-user1] by DomainChecker_EnhancerByCloudStack_73178ccf
2013-10-21 15:47:10,968 INFO  [user.snapshot.CreateSnapshotCmd] (Job-Executor-26:job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ]) VOLSS: createSnapshotCmd starts:1382350630968
2013-10-21 15:47:10,977 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-26:job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ]) Complete async job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create snapshot due to an internal error creating snapshot for volume 194
2013-10-21 15:47:13,057 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:null) SeqA 3-268: Processing Seq 3-268:  { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n  \"connections\": []\n}","wait":0}}] }
2013-10-21 15:47:13,175 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:null) SeqA 3-268: Sending Seq 3-268:  { Ans: , MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2013-10-21 15:47:13,975 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===START===  10.144.6.15 -- GET  command=queryAsyncJobResult&jobId=bcb81bb4-90bf-4d7f-b587-094f3edf1f5c&response=json&sessionkey=%2FIZ1HaelGzG022fKFel6n0xfjTo%3D&_=1382350939077
2013-10-21 15:47:13,987 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-1:null) Async job-22 = [ bcb81bb4-90bf-4d7f-b587-094f3edf1f5c ] completed


> [VMWARE]Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4907
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4907
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.1
>            Reporter: Sailaja Mada
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: issue.rar
>
>
> Steps:
> 1. Configure Adv Zone with VMWARE ESXI 5.0 using Zone wide primary storage
> 2. Deploy a VM using user account 
> 3. Move Zone wide primary storage into maintenance. With this System Vm's  got migrated to a xenserver host which is one more cluster in the setup.
> 4. Now tried to create ROOT volume snapshot of VMWARE user VM 
> 5. It failed saying "Failed to create snapshot due to an internal error creating snapshot for volume 194"
> But when looked at snapshot table. There is an entry created for this snapshot which is allowcated state. There is no snapshot in the Secondary storage. Issue is only about the entry in DB . This is getting displayed with listSnapshots from UI.
> Expected results :  When there is a failure to create snapshot , we should cleanup the entries created for that in the DB.
> mysql> select * from snapshots;
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+-----------------------------------+--------------------------------------+---------------+------------------+------------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id | status    | path | name                              | uuid                                 | snapshot_type | type_description | size       | created             | removed | backup_snap_id | swift_id | sechost_id | prev_snap_id | hypervisor_type | version | s3_id |
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+-----------------------------------+--------------------------------------+---------------+------------------+------------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> |  1 |              1 |          3 |         1 |       194 |                1 | BackedUp  | NULL | instance1_ROOT-194_20131021090425 | c12c752d-3743-48fe-a29e-f3c79efb4548 |             0 | MANUAL           | 2147483648 | 2013-10-21 09:04:25 | NULL    | NULL           |     NULL |       NULL |         NULL | VMware          | 2.2     |  NULL |
> |  2 |              1 |          3 |         1 |       194 |                1 | Allocated | NULL | instance1_ROOT-194_20131021094701 | cf15f6f1-98be-4587-bc59-53e000dabb41 |             0 | MANUAL           | 2147483648 | 2013-10-21 09:47:01 | NULL    | NULL           |     NULL |       NULL |         NULL | VMware          | 2.2     |  NULL |
> |  3 |              1 |          3 |         1 |       194 |                1 | Allocated | NULL | instance1_ROOT-194_20131021100210 | 02762645-c8a0-455f-8e73-5c2a5c90057b |             0 | MANUAL           | 2147483648 | 2013-10-21 10:02:10 | NULL    | NULL           |     NULL |       NULL |         NULL | VMware          | 2.2     |  NULL |
> |  4 |              1 |          3 |         1 |       194 |                1 | Allocated | NULL | instance1_ROOT-194_20131021101710 | c9d0f606-1410-475a-833b-ffdf780db765 |             0 | MANUAL           | 2147483648 | 2013-10-21 10:17:10 | NULL    | NULL           |     NULL |       NULL |         NULL | VMware          | 2.2     |  NULL |
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+-----------------------------------+--------------------------------------+---------------+------------------+------------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> 4 rows in set (0.00 sec)
> mysql>
> [root@ec2 management]# cd /mnt/secondary/
> [root@ec2 secondary]# ls
> snapshots  systemvm  template  volumes
> [root@ec2 secondary]# cd snapshots/
> [root@ec2 snapshots]# ls
> 3
> [root@ec2 snapshots]# ls -lR
> .:
> total 4
> drwxr-xr-x. 3 root root 4096 Oct 21 14:40 3
> ./3:
> total 4
> drwxr-xr-x. 3 root root 4096 Oct 21 14:40 194
> ./3/194:
> total 4
> drwxr-xr-x. 2 root root 4096 Oct 21 14:46 97440b36-03ce-47dd-815a-b25d614701b0
> ./3/194/97440b36-03ce-47dd-815a-b25d614701b0:
> total 449780
> -rw-r--r--. 1 root root 459654656 Oct 21 14:46 97440b36-03ce-47dd-815a-b25d614701b0-disk0.vmdk
> -rw-r--r--. 1 root root      6279 Oct 21 14:46 97440b36-03ce-47dd-815a-b25d614701b0.ovf
> [root@ec2 snapshots]# 



--
This message was sent by Atlassian JIRA
(v6.1#6144)