cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rayees Namathponnan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2040) VM with snapshot not getting destroyed during account delation
Date Tue, 16 Apr 2013 00:26:15 GMT
Rayees Namathponnan created CLOUDSTACK-2040:
-----------------------------------------------

             Summary: VM with snapshot not getting destroyed during account delation
                 Key: CLOUDSTACK-2040
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2040
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Snapshot
    Affects Versions: 4.2.0
         Environment: Master build
KVM and VMware
            Reporter: Rayees Namathponnan
             Fix For: 4.2.0
         Attachments: CLOUDSTACK-2040.rar

Step 1 : Create new build from master build 
Step 2 : Configure advanced zone
Step 3 set expunge.delay = 60 and expunge.interval = 60
Step 4 : Create an account 
Step 5 : Deploy and VM and take this VM's ROOT volume snapshot
Step 6 : Delete the account 

Actual Result 

Account is getting delete, but snapshot and VM not getting destoryed after 60 sec

Observed below null pointer exception in log 

2013-04-15 17:24:10,117 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) ===END===  10.216.133.58
-- GET  command=deleteAccount&response=json&sessionkey=GABpOjtD54ewGUFQ%2Bqdl%2FvklZaQ%3D&id=b5f159f3-1127-4876-929c-43d4d314c31e&_=1366071684428
2013-04-15 17:24:10,134 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-972) Executing
org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-972
2013-04-15 17:24:10,188 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-1:job-972) Removed
account 213
2013-04-15 17:24:10,268 WARN  [cloud.user.AccountManagerImpl] (Job-Executor-1:job-972) Failed
to cleanup account Acct[213-ray] due to 
java.lang.NullPointerException
	at com.cloud.agent.api.SnapshotCommand.<init>(SnapshotCommand.java:56)
	at com.cloud.agent.api.DeleteSnapshotBackupCommand.<init>(DeleteSnapshotBackupCommand.java:89)
	at com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:700)
	at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:554)
	at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:523)
	at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1188)
	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
	at org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177)
	at org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118)
	at org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100)
	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
	at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:722)
2013-04-15 17:24:10,284 INFO  [cloud.user.AccountManagerImpl] (Job-Executor-1:job-972) Cleanup
for account 213 is needed.
2013-04-15 17:24:10,292 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-972) Complete
async job-972, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse@5a4f6575


Expected Result

Account and associated VM and snapshot should be removed after 60 sec 

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