[
https://issues.apache.org/jira/browse/CLOUDSTACK-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748015#comment-13748015
]
Animesh Chaturvedi commented on CLOUDSTACK-4454:
------------------------------------------------
Applied to 4.2
> object_store - Not able to delete secondary storage when existing snapshots
> are deleted.
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4454
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: Build from 4.2
> Reporter: Sangeetha Hariharan
> Assignee: Min Chen
> Priority: Critical
> Fix For: 4.2.0, 4.2.1
>
>
> object_store - Not able to delete secondary storage when existing snapshots
> are deleted.
> Steps to reproduce the problem:
> Have a zone with 2 NSF secondary stores - ss1 and ss2.
> Deploy few Vms and take few snapshots.
> Delete all the snapshots that reside in ss2.
> Now try to delete ss2.
> Deletion fails with following error message:
> "Cannot delete image store with active snapshots backup!"
> Management server logs:
> 2013-08-22 10:13:35,466 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
> === START=== 10.215.3.9
> -- GET command=deleteImageStore&id=7b7ed196-fa00-4cd8-a606
>
> -b743cd64cfd9&response=json&sessionkey=pk9TsSw2pRHDZg2GsRmnZYONBKU%3D&_=13771920
> 39022
> 2013-08-22 10:13:35,475 INFO [cloud.api.ApiServer] (catalina-exec-12:null)
> Cannot delete image store with active snapshots backup!
> mysql> select * from image_store;
> +----+------+---------------------+----------+---------------------------------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
> | id | name | image_provider_name | protocol | url
> | data_center_id | scope | role | uuid
> | parent | created
> | removed | total_size | used_bytes |
> +----+------+---------------------+----------+---------------------------------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
> | 1 | ss1 | NFS | nfs |
> nfs://10.223.110.232/export/home/sangeetha/42-ipv6/secondary/ |
> 1 | ZONE | Image | cb921af8-83fa-4b04-a1fd-2a0970e3d16d |
> 036a3728-d869-3d9a-b590-bd8cbf5b2c14 | 2013-08-20 21:52:22 | NULL |
> NULL | NULL |
> | 2 | ss2 | NFS | nfs |
> nfs://10.223.110.232/export/home/sangeetha/42-ipv6/secondary2 |
> 1 | ZONE | Image | 7b7ed196-fa00-4cd8-a606-b743cd64cfd9 |
> 0653a328-9bb3-321c-943d-f5164eb2d62f | 2013-08-21 23:46:45 | NULL |
> NULL | NULL |
> | 3 | ss3 | NFS | nfs |
> nfs://10.223.110.232/export/home/sangeetha/42-ipv6/secondary3 |
> 1 | ZONE | Image | 4598a3fd-7b69-4e3f-9178-36799b5755b1 |
> 71490b8f-f8fd-3f54-b280-ded7eebee441 | 2013-08-22 17:17:57 | NULL |
> NULL | NULL |
> +----+------+---------------------+----------+---------------------------------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
> 3 rows in set (0.00 sec)
> mysql> select store_id , store_role, snapshot_id , state from
> snapshot_store_ref;
> +----------+------------+-------------+-----------+
> | store_id | store_role | snapshot_id | state |
> +----------+------------+-------------+-----------+
> | 1 | Image | 1 | Ready |
> | 1 | Primary | 2 | Ready |
> | 1 | Image | 2 | Ready |
> | 1 | Primary | 3 | Destroyed |
> | 2 | Image | 3 | Destroyed |
> | 1 | Primary | 4 | Destroyed |
> | 2 | Image | 4 | Destroyed |
> +----------+------------+-------------+-----------+
> 7 rows in set (0.03 sec)
> mysql>
--
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
