You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/05/02 22:28:20 UTC

[jira] [Commented] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

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

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

Commit 81b4731e3b5265943017f88b850421154184f7c5 in cloudstack's branch refs/heads/master from [~SamSchmit]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=81b4731 ]

CLOUDSTACK-6472 listUsageRecords: Pull information from removed items as well, fixing NPEs/Null UUIDs with usage API calls.

Signed-off-by: Sebastien Goasguen <ru...@gmail.com>


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