cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "edison su (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-4907) Volume Snapshot Entries are not deleted from DB when there is a failure to create Snapshot
Date Fri, 08 Nov 2013 23:18:17 GMT

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

edison su reassigned CLOUDSTACK-4907:
-------------------------------------

    Assignee: edison su  (was: Nitin Mehta)

> 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: Storage Controller
>    Affects Versions: 4.2.1
>         Environment: Edited the title
>            Reporter: Sailaja Mada
>            Assignee: edison su
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: issue.rar, listsnaps.png
>
>
> 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)

Mime
View raw message