You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2014/06/10 12:29:02 UTC
[jira] [Updated] (CLOUDSTACK-6472) listUsageRecords generates NPEs
for expunging instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajani Karuturi updated CLOUDSTACK-6472:
----------------------------------------
Fix Version/s: 4.3.1
4.4.0
> listUsageRecords generates NPEs for expunging instances
> -------------------------------------------------------
>
> Key: CLOUDSTACK-6472
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Usage
> Affects Versions: 4.3.0
> Environment: linux
> Reporter: Pierre-Yves Ritschard
> Fix For: 4.4.0, 4.3.1
>
> Attachments: 0001-handle-removed-entities.patch
>
>
> The listUsageRecords API command, pulls down the list of usage records in the cloud_usage database and augments records with information pulled from the cloud database.
> When dealing with instance records, only instances which are do not have a value for the removed field are considered. Unfortunately, since the output of _entityMgr.findById is not checked this means that Null Pointer Exceptions are generated when trying to access the output for expunged VMs.
> The attached patch fixes the issue and applies a similar fix for other similar cases.
--
This message was sent by Atlassian JIRA
(v6.2#6252)