vCenterへのvSAN HCL同期が、以下のエラーで失敗します: "Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API"

Products

• VMware SDDC Manager

Issue/Introduction

JSONファイル(https://vvs.broadcom.com/service/vsan/all.json)が更新され、vCenterのvSAN HCLとSDDC Manager間の同期が行われる際、「Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API（VSAN HCL DBのアップロードに失敗しました。APIが成功した後も、vCenter内のVSAN HCL DBのタイムスタンプが更新されていません）」というエラーで失敗します。なお、SDDC Managerの事前チェックへの影響はありません。

同期を試行すると、以下のログが表示されます。

/var/log/vmware/vcf/lcm/lcm-debug.log

yyyy-mm-ddT11:43:54.870+0800 INFO  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] For the new HCL, the timestamp is 1763007154 & jsonUpdatedTime is 1763007120
yyyy-mm-ddT11:43:54.871+0800 DEBUG [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] We found entry for jsonUpdatedTime, hence using jsonUpdatedTime as timestamp value for new HCL
yyyy-mm-ddT11:43:58.883+0800 WARN  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] Expected HCL timestamp 1763007120 is NOT same as actual HCL timestamp 1762978320
yyyy-mm-ddT11:43:59.178+0800 INFO  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] For the new HCL, the timestamp is 1763007154 & jsonUpdatedTime is 1763007120
yyyy-mm-ddT11:43:59.178+0800 DEBUG [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] We found entry for jsonUpdatedTime, hence using jsonUpdatedTime as timestamp value for new HCL
yyyy-mm-ddT11:44:02.646+0800 WARN  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] Expected HCL timestamp 1763007120 is NOT same as actual HCL timestamp 1762978320
yyyy-mm-ddT11:44:02.953+0800 INFO  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] For the new HCL, the timestamp is 1763007154 & jsonUpdatedTime is 1763007120
yyyy-mm-ddT11:44:02.953+0800 DEBUG [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] We found entry for jsonUpdatedTime, hence using jsonUpdatedTime as timestamp value for new HCL
yyyy-mm-ddT11:44:06.563+0800 WARN  [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.p.i.vsan.VsanHealthService,HCL-Sync-1] Expected HCL timestamp 1763007120 is NOT same as actual HCL timestamp 1762978320
yyyy-mm-ddT11:44:06.585+0800 ERROR [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.s.impl.VsanHclSyncRunner,HCL-Sync-1] Failed to update vSAN HCL in vCenter: <hostname> and cluster <cluster_name> with exception Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API.
yyyy-mm-ddT11:44:06.585+0800 ERROR [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.s.impl.VsanHclSyncRunner,HCL-Sync-1] Uploading vSAN HCL to vCenter: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx failed with exception: Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API.
com.vmware.evo.sddc.lcm.model.error.LcmException: Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API.

Environment

VMware Cloud Foundation 4.5.x

VMware Cloud Foundation 5.x

Cause

vCenter Server とSDDC Manager の両方がUTC(協定世界時)以外のタイムゾーンに設定されているため、vSAN HCLの更新時にタイムスタンプの比較が正しく行われません。その結果、処理時間が大幅に増大し、最終的に失敗します。

Resolution

1. vCenterのタイムゾーンをUTCに変更します(システムのタイム ゾーンおよび時刻同期の設定の構成)。
2. SDDC ManagerのタイムゾーンをUTCに更新します。
3. SDDC ManagerとvCenterの両方を再起動します。

Additional Information

Syncing vSAN HCL to vCenter is failing with the error : "Failed to upload the VSAN HCL DB. VSAN HCL DB timestamp is not updated in vCenter even after successful API"