You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjay Tripathi (JIRA)" <ji...@apache.org> on 2014/11/04 13:26:34 UTC
[jira] [Resolved] (CLOUDSTACK-7835) Deleted volumes with null UUID
and no removed timestamp in database still appear
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Tripathi resolved CLOUDSTACK-7835.
-----------------------------------------
Resolution: Fixed
> Deleted volumes with null UUID and no removed timestamp in database still appear
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7835
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7835
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Volumes
> Environment: XS 6.2
> Latest code from 4.5
> Reporter: Sanjay Tripathi
> Assignee: Sanjay Tripathi
> Fix For: 4.5.0
>
>
> Occasionally when CS deletes a volume, it does not fully delete it out of the database.
> Instead an entry is left behind with a null UUID and no removal timestamp, so the volume appears in the CS UI. However any attempt to view the volume's information will result in an exception.
> And since there is no UUID, there is no way I know of to ask CS's API to do anything with them.
> mysql> select id,name,uuid,created,attached from volumes where removed is null order by id asc;
> id name uuid created attached
> 8 vol3 NULL 2014-10-16 23:16:34 2014-10-16 23:17:47
> 11 vol4 NULL 2014-10-17 02:54:44 2014-10-17 02:55:47
> 15 vol6 NULL 2014-10-17 11:09:32 2014-10-17 11:11:23
> 19 vol10 NULL 2014-10-17 14:54:35 2014-10-17 14:56:09
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)