[jira] [Closed] (CLOUDSTACK-286) listvolumes doesnt show a data volume thats attached to a vm which is in destroyed state.

["Ahmad Emneina (JIRA)" <ji...@apache.org>]

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

Ahmad Emneina closed CLOUDSTACK-286.
------------------------------------


this was observed on a Citrix CloudPlatform release and verified NOT to be an issue with incubating-apache prerelease candidate for 4.0.

Management server build:

[root@dummy]# cloud-sccs
Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

                
> listvolumes doesnt show a data volume thats attached to a vm which is in destroyed state.
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-286
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-286
>             Project: CloudStack
>          Issue Type: Bug
>          Components: API, Management Server
>    Affects Versions: 4.0.0
>            Reporter: Ahmad Emneina
>            Assignee: Mice Xia
>
> We should still show valid volumes. This on the surface appears scary, since the data volume disappears when one calls destroy vm on a vm with a data volume... We should either detach the volume right away when destroying or add some state where we can still have these volumes appear in a listvolumes call.
> Steps to reproduce:
> 1. create a vm
> 2. create a data volume
> 3. attache volume to vm
> 4. destroy vm
> 5. issue a listvolumes api call (before the vm gets expunged)

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