HCX - Service Mesh deployment fails

Products

• VMware HCX

Issue/Introduction

• HCX Service Mesh deployment fails with the error below:
  

  Appliance operation failed for applianceId ######-#####-#####-####### with error Failed to configure underlay metrics collection Interconnect Service Workflow configureUnderlayMetricsCollection failed. Error: Failed to write the certificate for the appliance [######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######].The requested operation has been completed successfully, however underlay metric collection will not work. For underlay to work for the appliance, the appliance needs to be force synced, Failed to write the certificate for the appliance [######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######, ######-#####-#####-#######,######-#####-#####-#######, ######-#####-#####-#######].The requested operation has been completed successfully, however underlay metric collection will not work. For underlay to work for the appliance, the appliance needs to be force synced

• The following error in HCX manager /common/logs/admin/app.log shows that with '/' present in the service mesh name considers as an extra path leading to an incorrect directory location while fetching the necessary files required to deploy the service mesh.
• For example, if the Service Mesh name is "AD/Service_Mesh", you will see an error stating "No such file or directory" in /common/logs/admin/app.log


  2024-11-20 06:47:57.438 UTC [InterconnectService_SvcThread-8776, J:9a43668c, , TxId: TxId: ######-######-######-######] ERROR c.v.v.h.s.i.ConfigureUnderlayMetricsCollection- Failed to write the certificate for the appliance AD/Service_Mesh-IX-R1
  java.io.FileNotFoundException: /common/cs/gw_certs/AD/Service_Mesh-IX-R1_1732064746530.pem (No such file or directory)

Environment

HCX

Cause

Service mesh deployment fails due to the special character '/' present in the service mesh name.

 

Resolution

Deploy the Service Mesh without the special character '/'

Additional Information

Service Mesh upgrade/deploy failure issue has also been noticed in HCX 4.10 if the Service Mesh has a "space" in its name. However, this issue is fixed in HCX 4.10.2. For more information, access: VMware HCX 4.10.2 Release Notes.