cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-1109) Ipv6 - Unable to expunge User Vms that are "Destroyed".
Date Fri, 01 Feb 2013 00:27:13 GMT
Sangeetha Hariharan created CLOUDSTACK-1109:

             Summary: Ipv6 - Unable to expunge User Vms that are "Destroyed".
                 Key: CLOUDSTACK-1109
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.1.0
         Environment: Latest build from IPv6 branch.
            Reporter: Sangeetha Hariharan
            Assignee: Sheng Yang
             Fix For: 4.1.0

Ipv6 - Unable to expunge User Vms that are "Destroyed".

Steps to reproduce the problem:

Create a Ipv6 network.

Deploy few Vms in this network.

Destroy one of the VMs.

After Expunge Interval passes, we see the following exception in the management server logs:

User Vms are stuck in "Expunging" state.

Following exception seen in management server logs:

2013-02-01 00:15:31,410 DEBUG [cloud.vm.VirtualMachineManagerImpl] (UserVm-Scavenger-1:null)
Stopped called on VM[User|n1-vm1] but the state is Destroyed
2013-02-01 00:15:31,422 DEBUG [cloud.capacity.CapacityManagerImpl] (UserVm-Scavenger-1:null)
VM state transitted from :Destroyed to Expunging with event: ExpungeOperationvm's original
host id: 1 new host id: null host id before state transition: null
2013-02-01 00:15:31,422 DEBUG [cloud.vm.VirtualMachineManagerImpl] (UserVm-Scavenger-1:null)
Destroying vm VM[User|n1-vm1]
2013-02-01 00:15:31,422 DEBUG [cloud.vm.VirtualMachineManagerImpl] (UserVm-Scavenger-1:null)
Cleaning up NICS
2013-02-01 00:15:31,422 DEBUG [] (UserVm-Scavenger-1:null)
Cleaning network for vm: 3
2013-02-01 00:15:31,432 DEBUG [] (UserVm-Scavenger-1:null) Service
SecurityGroup is not supported in the network id=204
2013-02-01 00:15:31,434 DEBUG [] (UserVm-Scavenger-1:null) Deallocate
network: networkId: 204, ip: null
2013-02-01 00:15:31,437 DEBUG [db.Transaction.Transaction] (UserVm-Scavenger-1:null) Rolling
back the transaction: Time = 1 Name =  deallocate; called by -Transaction.rollback:882-Transaction.removeUpTo:825-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-GenericDaoBase.remove:1663-DatabaseCallback.intercept:34-DirectNetworkGuru.deallocate:235-DatabaseCallback.intercept:34-NetworkManagerImpl.removeNic:1838-NetworkManagerImpl.cleanupNics:1822-VirtualMachineManagerImpl.advanceExpunge:402
2013-02-01 00:15:31,437 WARN  [cloud.vm.UserVmManagerImpl] (UserVm-Scavenger-1:null) Unable
to expunge VM[User|n1-vm1]
java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.String
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(
        at java.util.concurrent.FutureTask.runAndReset(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

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