[
https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625762#comment-13625762
]
Musayev, Ilya commented on CLOUDSTACK-1868:
-------------------------------------------
Francois,
I've raised this issue in past, it appears it's going to be resolved with
CLOUDSTACK-669 - hopefully in 4.2 release.
Kelven mentioned he began the work on this feature, please review the contents
of ISSUE 669, there are other features VMWARE that may benefit with better VM
SYNC.
Regards
ilya
> GetVmStatsCommand throws NullPointerException with VMWare
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-1868
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0
> Reporter: Francois Gaudreault
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.1.0
>
> Attachments: management.log
>
>
> We see bunch of these in the log files of CloudStack. Looks like the
> GetVmStatsCommand crash with a Null pointer exception. We don't think it's
> permission related since our CS user on vSphere can see all performance and
> VM statistics using the vSphere client.
> INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined
> to be up and running
> ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot)
> Unable to execute GetVmStatsCommand due to : Exception:
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM
> statistics.
> ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot)
> Unable to execute GetVmStatsCommand due to : Exception:
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM
> statistics.
--
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
