Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 4 Nov 2014 12:25:34 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12752658.1415092608000.408170.1415103934270@Atlassian.JIRA>
In-Reply-To: <JIRA.12752658.1415092608000@Atlassian.JIRA>
References: <JIRA.12752658.1415092608000@Atlassian.JIRA>
 <JIRA.12752658.1415092608709@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-7835) Deleted volumes with null UUID
 and no removed timestamp in database still appear
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on CLOUDSTACK-7835:
-------------------------------------------------------------

Commit a53d39c1b687df22768613d556637c34354cb96b in cloudstack's branch refs/heads/4.5 from [~sanjay.tripathi]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a53d39c1 ]

CLOUDSTACK-7835: Deleted volumes with null UUID and no removed timestamp in database still appear.
Also removed CREATING -> DESTROY via DESTROYREQUESTED, which was causing the volume to get stuck in expunging
state.


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