cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3376) NPE: resource count calculation from the account manager on account cleanup
Date Wed, 17 Jul 2013 07:14:50 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710819#comment-13710819
] 

ASF subversion and git services commented on CLOUDSTACK-3376:
-------------------------------------------------------------

Commit 21b1c9449a1289db9fa92c2ec76a936006100ab3 in branch refs/heads/master from [~sanjay.tripathi]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=21b1c94 ]

CLOUDSTACK-3376: NPE: resource count calculation from the account manager on account cleanup

This issue is happing because of the steps the code follow to cleanup the account.
The cleanupAccount was deleting the entries from the resource_limit and
resource_count table and performing further cleaning afterwards. Ideally, deletion
of entries from resourceLimit and resourceCount should be the last step in
cleanupAccount process.

Signed-off-by: Prasanna Santhanam <tsp@apache.org>

                
> NPE: resource count calculation from the account manager on account cleanup
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3376
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3376
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Assignee: Sanjay Tripathi
>             Fix For: 4.2.0
>
>         Attachments: 483.tar.bz2
>
>
> During account cleanup on one of the accounts the following NPE was encountered on a
template that had failed to delete.
> Attaching complete logs. This was an XCP 1.6 setup of cloudstack master
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,066 DEBUG
[db.Transaction.Transaction] (AccountChecker-1:null) Rolling back the transaction: Time =
2 Name =  -AccountManagerImpl$AccountCleanupTask.run:1481-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-ResourceLimitManagerImpl.recalculateResourceCount:702-HypervisorTemplateAdapter.delete:277-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-TemplateManagerImpl.delete:748-AccountManagerImpl.cleanupAccount:592-AccountManagerImpl$AccountCleanupTask.run:1488-Executors$RunnableAdapter.call:471
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,066 WARN
 [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete template while removing
account: Public template-5D26S2 due to: 
> Jul  4 23:46:44 java.lang.NullPointerException  
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:277)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:748)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com     at java.lang.Thread.run(Thread.java:679)
> Jul  4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 06:46:44,067 WARN
 [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete templates while
removing account id=22

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