[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-tabpanelfocusedCommentId=13990607#comment-13990607 ] ASF subversion and git services commented on CLOUDSTACK-6472: - Commit e8047e11db7ef2bdc44bbedfdc47e63c55f080c5 in cloudstack's branch refs/heads/4.3 from [~SamSchmit] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e8047e1 ] CLOUDSTACK-6472 (4.3 specific) listUsageRecords: Pull information from removed items as well, fixing NPEs/Null UUIDs with usage API calls. Signed-off-by: Sebastien Goasguen run...@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)
[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-tabpanelfocusedCommentId=13990766#comment-13990766 ] ASF subversion and git services commented on CLOUDSTACK-6472: - Commit 3a3457e7132d22f52aa38179d40a6eb9b0b29677 in cloudstack's branch refs/heads/4.4 from [~SamSchmit] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3a3457e ] CLOUDSTACK-6472 listUsageRecords: Pull information from removed items as well, fixing NPEs/Null UUIDs with usage API calls. 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)
[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-tabpanelfocusedCommentId=13988617#comment-13988617 ] Pierre-Yves Ritschard commented on CLOUDSTACK-6472: --- This can now be closed 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)
[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-tabpanelfocusedCommentId=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 run...@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)
[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-tabpanelfocusedCommentId=13988205#comment-13988205 ] ASF subversion and git services commented on CLOUDSTACK-6472: - Commit fe84b674c14b6494770b489100e92a116b3b1f49 in cloudstack's branch refs/heads/4.4-forward from [~SamSchmit] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fe84b67 ] CLOUDSTACK-6472 listUsageRecords: Pull information from removed items as well, fixing NPEs/Null UUIDs with usage API calls. 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)