DSM System Backup Repository Configuration Fails with Webhook Timeout

Products

• VMware Data Services Manager for VCF

Issue/Introduction

• When attempting to configure the S3 endpoint for the System Backup Repository in VMware Data Services Manager (DSM), the configuration fails with the following internal error:

Internal error occurred: failed calling webhook "backuplocations.databases.dataservices.vmware.com": failed to call webhook: Post "https://webhooks:9443/mutate-databases-dataservices-vmware-com-v1alpha1-backuplocation?timeout=10s": context deadline exceeded

Environment

VMware Data Services Manager 9.x

Cause

• This issue occurs because the DSM appliance lacks a direct connection to the configured S3 endpoint.
  
  
• As of the current design, DSM does not support local proxy configurations for backup repository traffic.
  
  
• When the webhook attempts to validate the backup location, the connection attempt times out after 10 seconds, exceeding the hardcoded webhook deadline.

Resolution

• Ensure the DSM appliance has a direct connection to the S3 endpoint that does not require an HTTP/HTTPS proxy.