ESXI Component synchronization fails connecting to the incorrect depot

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

 

ESXI Component synchronization fails after configuration of offline http depot connection without using the supported API method. 

The following workaround was applied: 

• To enable the VCF Installer to allow a non-HTTPS connection to your offline depot, you will need to add lcm.depot.adapter.httpsEnabled=false to following configuration file /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties

Environment

VMware Cloud Foundation 9.1 

Cause

Setting offline depot using http without using the API.

• HTTP Offline Depot configuration is only support through API configuration in 9.1  
• UMDS in the offline depot was meant to be configured over https and not http.

OfflineDepotServiceImpl (scheduler path) always calls OfflineDepotUrlUtils with isHttpsEnabled=true,
constructing an HTTPS URL regardless of how the depot was configured. The API handler (depot settings path) uses isHttpsEnabled=false (HTTP), matching the actual depot. Because two different URLs are registered in UMDS, cleanup at removal time — which also uses isHttpsEnabled=false — only removes the HTTP entry and leaves the HTTPS one stranded.

Resolution

 

1. Take a snapshot of the SDDC Manager
2. SSH in to the SDDC Manager appliance using the vcf user account
3. Navigate to /opt/vmware/vmware-umds/bin
4. View configuration of UMDS: 
   

   1. /opt/vmware/vmware-umds/bin/vmware-umds -G

5. remove the HTTPS URL for the offline depot:
   

   1. vmware-umds -S --remove-url https://<IP_ADDRESS>:8000/umds-patch-store/.../index.xml

6. Rerun the ESXI component Synchronizes now