SOS health report on the VCF 4.x, 5.0.x and 5.1.x would incorrectly report NTP check fail for Aria Components

Products

• VMware SDDC Manager

Issue/Introduction

SOS health report for NTP check would fail for random components of Aria and would report NTP sycn/check has failed, pointing to vrops nodes or other Aria components. 

 

sos.log: 

2023-12-20T03:26:34.900+0000 ERROR [vcf_sos] [vrealizehelper.py::_parallel_check_vrealize_products_ntp_configured::1707::_parallel_check_vrealize_products_ntp_configuredThread1] Unknown Exception occurred during NTP check for vRealize products: vrops_node3.lab.local, please refer sos.log for more details or contact support.Error : AttributeError("'NoneType' object has no attribute 'split'")

While the actual NTP from the sos would look like: 

|  9  |    vRSLCM : vrslcm01.lab.local      | NTP Status | GREEN |
|  10 |    vrops : vrops_node1.lab.local    | NTP Status | GREEN |
|  11 |    vrops : vrops_node2.lab.local    | NTP Status | GREEN |
|  12 |    vrops : vrops_node3.lab.local    | NTP Status | GREEN |
+-----+---------------------------------------------+------------+-------+

When the actual end point components are checked we can see, the NTP is configured correctly, and time is in sync. 
The validation can be done on both vrslcm level and on the actual endpoints where the report is pointed towards. 

Purpose: 
The purpose of this article is to explain the workflow of the NTP query to the Aria components by SOS from the sddc manager and identify the issue and to triage and identify the cause quickly.

Environment

VCF 4.x, VCF 5.0.x, VCF 5.1.x

Cause

• SoS performs NTP checks on following Aria products (vrli, vrops, vra, vrslcm), and fetches vrslcm environment details using https://<vrslcm>/lcm/lcops/api/environments.
• it also checks for "ntp" details for vrli, vrops, vra nodes and its properties. If "ntp" details are not found/Null - the check results in failure.  
• This causes below exception, hence the SoS NTP health check failure
      AttributeError: 'NoneType' object has no attribute 'split'

In addition, the Aria components like the Cloud proxies and the remote collectors' NTP values are not managed/updated by vRSLCM and will not have an NTP property value, and therefore will report NULL when queried.  
Hence on VCF infra with cloud proxies and remote collector components Customers will more often see the SOS report.json, reporting an error for one of the Aria components. 

Resolution

This issue is fixed on VCF 5.2 

To resolve issue with NTP check for VRA please use the following scripts.  

• vcf5110_sos_workaround_PR3424661.zip
•  
• vcf5200_sos_workaround_PR3424646.zip

For workarounds on previous versions please reach out to the VCF Global Support Team.