HCX - VM with Sentinel agent installed does not show in HCX inventory
book
Article ID: 321565
calendar_today
Updated On:
Products
VMware HCXVMware vSphere ESXi
Issue/Introduction
Help identify a known issue that prevents the migration of a VM with OSAM.
Under certain circumstances a VM with HCX Sentinel agent installed will not show as candidate for OSAM in HCX UI. The issue can be confirmed by reviewing the logs.
/var/log/vmware/hcx/osam/sentinel.log on the source system: ERROR [Thread-3] c.v.h.F.ManagerReSTServer$RestAPIHandler - Error getting system configuration java.lang.NumberFormatException: For input string: "5003571993"
/common/logs/admin/app.log: app.log:YYYY-MM-DD [SentinelInventoryService_SvcThread-8449, Ent: HybridityAdmin, , TxId: ########-####-####-####-########d63d] ERROR c.v.v.h.s.s.QuerySentinelInventoryJob- Exception while trying to get configuration for sentinel ########-####-####-####-########7ef7: com.vmware.vchs.hybridity.adapters.https.HttpRequestException: Status code=500, reason=Internal Server Error, result=
Environment
VMware HCX
Cause
The Sentinel agent experiences an exception when parsing CPU statistics due to the integer length when the GuestOS uptime is very long.
IMPORTANT: This issue happens in HCX release 4.0.0 and it affects VMs running Linux Guest OS only. Previous releases and Windows Guest OS are not impacted.
Resolution
This issue is resolved in VMware HCX 4.0.1
Workaround: If at all possible, the VM could be rebooted to reset the uptime.
Additional Information
Impact/Risks: This issue prevents the Sentinel agent from getting the VM configuration required to include it in the HCX inventory for OSAM.