[
https://issues.apache.org/jira/browse/CLOUDSTACK-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644600#comment-13644600
]
ASF subversion and git services commented on CLOUDSTACK-2279:
-------------------------------------------------------------
Commit a0dbf8909058dba202c057f5b9d589026399c6ef in branch refs/heads/master
from Marcus Sorensen <mar...@betterservers.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a0dbf89 ]
Look for null pointer on account id before trying to update usage when releasing
an IP. This seems to be possible if expunge fails at some point after freeing
an IP, on subsequent expunge tries the IP is freed already and gets null pointer
when looking for account id.
BUG-ID: CLOUDSTACK-2279
Bugfix-for: 4.1,4.2
Signed-off-by: Marcus Sorensen <mar...@betterservers.com> 1367251304 -0600
> Fail to clean up networks if expunge initially had a problem
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-2279
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2279
> 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, 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Priority: Critical
> Fix For: 4.1.0, 4.2.0
>
>
> Noticed today that I had some VMs stuck in expunging state. Looked into it
> and found that expunge had failed for reasons that are cleared now, but
> subsequent tries were failing because the IP was already released, and the
> usage event was getting a null pointer when trying to look up the account.
--
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
