cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2003) Deleting domain while deleted account is cleaning up leaves VMs expunging forever due to 'Failed to update resource count'
Date Thu, 11 Apr 2013 16:11:18 GMT


ASF subversion and git services commented on CLOUDSTACK-2003:

Commit f12b328b337b4ad54fbe55ce029260002b0d7b49 in branch refs/heads/4.0 from Joe Brockmeier
[;h=f12b328 ]

CLOUDSTACK-2003: When accounts and domains are deleted, cleanup can fail,
leaving instances in eternal expunged state. This happens when a domain is
deleted while a deleted account is cleaning up. The cleanup looks for the domain
of the account and we hit a null pointer. Adding null pointer check.

Signed-off-by: Marcus Sorensen <> 1365695448 -0600

> Deleting domain while deleted account is cleaning up leaves VMs expunging forever due
to 'Failed to update resource count'
> --------------------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2003
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.1, 4.1.0, Future
>            Reporter: Marcus Sorensen
>            Priority: Blocker
>             Fix For: 4.0.2, 4.1.0, Future
> Marking this as a blocker because it requires admin to manually edit database to fix,
otherwise VMs can stack up forever in expunging under a certain scenario.
> Create a cloudstack zone
> Create a domain
> Create an account within the domain
> Launch VMs with the account
> Delete the account, this should begin stopping/destroying VMs associated with the account
> Before the account job is finished, delete the domain. Now Domain is gone and account
is gone, but associated VMs never clean up.
> Expunging will error out due to the domain missing:
> 2013-04-10 16:34:52,925 ERROR [cloud.resourcelimit.ResourceLimitManagerImpl] (Job-Executor-7:job-39)
Failed to update resource count for account
> 2013-04-10 16:34:53,019 WARN  [cloud.vm.UserVmManagerImpl] (Job-Executor-7:job-39) Concurrent
operations on expunging VM[User|7646b383-7cd7-48a1-a056-a48fb54111c8]
> Failed to transit state
> 	at
> 	at$InterceptorDispatcher.intercept(
> 	at
> 	at$InterceptorDispatcher.intercept(
> 	at
> 	at
> 	at
> 	at
> 	at
> If I manually re-enable the domain in the database, expunging completes. Then I can safely
delete the account.  This is a regression from the 4.0 behavior, according to our test suites,
 where account and domain could be safely removed and associated resources would clean up.

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