cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-3704) ListVolumes API is broken, shows expunging/expunged volumes as well
Date Mon, 22 Jul 2013 18:08:49 GMT


Alena Prokharchyk resolved CLOUDSTACK-3704.

    Resolution: Not A Problem

ListVolumes return volumes in all the states, including Expunging/Expunged, if Removed field
for the volume is NULL. 
There is one scenario when the volume can stay in those states with not null removed state:

* when the volume is being expunged (Expunging state) by the storage cleanup thread.
* when the volume is expunged from the backend by the storage cleanup thread, but the Removed
field wasn't updated yet. It shoudn't take more than millisecond though.

I've tested the listVolumes API, it never returns the Removed volumes. But if you see that
the volume stays in Expunged state with non-removed field for a long time, there might be
some problem in the cleanup volume process, and you have to debug it separately, and file
a separate bug for it.
> ListVolumes API is broken, shows expunging/expunged volumes as well
> -------------------------------------------------------------------
>                 Key: CLOUDSTACK-3704
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.2.0
>            Reporter: Koushik Das
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.2.0
> http://localhost:8096/client/api?command=listVolumes&listall=true is showing exounging/expunged
volumes as well.
> Due to this the UI is also displaying unnecessary volumes.

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:

View raw message