What are your expunge.delay and expunge.interval global params set to? On 10/9/12 11:53 PM, "Mice Xia (JIRA)" <[email protected]> wrote:
> > [ >https://issues.apache.org/jira/browse/CLOUDSTACK-286?page=com.atlassian.ji >ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473033 >#comment-13473033 ] > >Mice Xia commented on CLOUDSTACK-286: >------------------------------------- > >Ahmad, > >Sorry I'm a bit lost. Could you please post a complete API call? > >i'm trying to follow your steps but cannot reproduce it. >i'm doing this with a user account (non-root), create one VM, attach a >volume, destroy the VM, call listVolumes API. > >[Here is what my API url like] >http://1.1.1.220:8080/client/api?command=listVolumes&page=1&pagesize=20&re >sponse=xml&sessionkey=AdOvwx46SJ1mgjFVTE6uA92xZwo%3D&_=1349851169510 > >[Here is the Response] ><listvolumesresponse cloud-stack-version="4.0.0.2012-10-10T06:33:19Z"> > <count>2</count> > <volume> > <id>f99f5699-4a67-4afb-b1b9-0173a5970c44</id> > <name>test2</name> > <zoneid>d4e5d7b0-a606-41d1-9ea3-f81ee39eaf97</zoneid> > <zonename>foobar</zonename> > <type>DATADISK</type> > <deviceid>1</deviceid> > ><virtualmachineid>4f6257aa-4d97-45b9-8352-80c8742230b4</virtualmachineid> > <vmname>4f6257aa-4d97-45b9-8352-80c8742230b4</vmname> > <vmdisplayname>4f6257aa-4d97-45b9-8352-80c8742230b4</vmdisplayname> > <vmstate>Destroyed</vmstate> > <size>5368709120</size> > <created>2012-10-10T14:42:30+0800</created> > <state>Ready</state> > <account>foobar</account> > <domainid>384e77d9-89e2-4ff5-b279-0ee12e4958c2</domainid> > <domain>ROOT</domain> > <storagetype>shared</storagetype> > <diskofferingid>548957e6-18b2-4a60-a27d-09312cee00f5</diskofferingid> > <diskofferingname>Small</diskofferingname> > <diskofferingdisplaytext>Small Disk, 5 GB</diskofferingdisplaytext> > <storage>pri7</storage> > <attached>2012-10-10T14:42:36+0800</attached> > <destroyed>false</destroyed> > <isextractable>true</isextractable> > </volume> > <volume> > <id>cbedb2e5-73cc-4892-91ac-fab88bc71810</id> > <name>ROOT-5</name> > <zoneid>d4e5d7b0-a606-41d1-9ea3-f81ee39eaf97</zoneid> > <zonename>foobar</zonename> > <type>ROOT</type> > <deviceid>0</deviceid> > ><virtualmachineid>4f6257aa-4d97-45b9-8352-80c8742230b4</virtualmachineid> > <vmname>4f6257aa-4d97-45b9-8352-80c8742230b4</vmname> > <vmdisplayname>4f6257aa-4d97-45b9-8352-80c8742230b4</vmdisplayname> > <vmstate>Destroyed</vmstate> > <size>21474836480</size> > <created>2012-10-10T13:10:36+0800</created> > <state>Ready</state> > <account>foobar</account> > <domainid>384e77d9-89e2-4ff5-b279-0ee12e4958c2</domainid> > <domain>ROOT</domain> > <storagetype>shared</storagetype> > <storage>pri7</storage> > <destroyed>false</destroyed> > ><serviceofferingid>2d9ae057-0133-420d-9bf6-ff2377b1c65e</serviceofferingid >> > <serviceofferingname>Small Instance</serviceofferingname> > <serviceofferingdisplaytext>Small >Instance</serviceofferingdisplaytext> > <isextractable>true</isextractable> > </volume> ></listvolumesresponse> > > >> 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 > -- Æ
