incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmad Emneina (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-286) listvolumes doesnt show a data volume thats attached to a vm which is in destroyed state.
Date Wed, 10 Oct 2012 06:03:02 GMT

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

Ahmad Emneina reopened CLOUDSTACK-286:
--------------------------------------


The fact the volume should NOT be destroyed is reason enough to list it in a regular list
call, immediately after the vm its attached to is destroyed. The issue is, after re-testing...
that the data disk state is Destroyed, when the vm its attached to is destroyed. This remains
until the vm is expunged, then it is detached and in a listable stat again. I explained this
to Alex Huang recently and he thought this was definitely a bug.
                
> 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
>             Fix For: 4.1.0
>
>
> 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

Mime
View raw message