[
https://issues.apache.org/jira/browse/CLOUDSTACK-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-4471.
-----------------------------------
Resolution: Incomplete
Can't find any log in your attached mgt server log, regarding to vm: i-4-36-VM,
which has a volume is in allocated state, while the vm is in expunged state.
We do have the code to handle the situation, in case starting vm failed. For
whatever reason, as long as the vm is expunged, a method called, cleanupVolumes
will be called, which will destroy all the volumes belong to that vm. In this
case, the code will set volume's state to "Destroyed" and marked as removed.
Need more logs about what's happened for vm i-4-36-VM
> Error Instances leaving ROOT Volumes in expunging state and not getting
> updated as removed evenafter having the instances expunged
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4471
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4471
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.1
> Reporter: Sailaja Mada
> Assignee: edison su
> Priority: Critical
> Fix For: 4.2.1
>
> Attachments: volumelogs.rar
>
>
> Steps:
> 1.Configure Advzone with VMWARE
> 2. Set the expunge interval to lesser value
> 3. Enable storage.cleanup interval to lesser value
> 4. There is a case where user instances failed to deploy and they are into
> ERROR state
> Obseravation:
> 1. There is a root DISK created as part of this deployment. When VM got
> expunged , these ROOT disks are moved to expunging state . But these are not
> updated as removed.
> 2. With that list Volumes we get to see all these volumes being displayed
> <volume><id>fe7cc918-dd31-4925-9dd0-9917807d051a</id><name>ROOT-36</name><zoneid>efb00e64-4f4d-4582-818c-cb80446d5e5c</zoneid><zonename>307XenZone1</zonename><type>ROOT</type><deviceid>0</deviceid><virtualmachineid>1043592d-9df7-490b-a408-0dd7cdb80239</virtualmachineid><vmname>1043592d-9df7-490b-a408-0dd7cdb80239</vmname><vmstate>Expunging</vmstate><size>2147483648</size><created>2013-08-22T14:47:16+0530</created><state>Allocated</state><account>vmwareuser1</account><domainid>ca370a5c-0b19-4358-a757-58549a2c29ed</domainid><domain>cdc</domain><storagetype>shared</storagetype><destroyed>false</destroyed><serviceofferingid>3c1dacb5-6629-432b-b093-f260067a078c</serviceofferingid><serviceofferingname>host13</serviceofferingname><serviceofferingdisplaytext>host13</serviceofferingdisplaytext><isextractable>true</isextractable><displayvolume>false</displayvolume></volume><volume>
--
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
