VCFA default namespace is not synced to DSM because the name is too long

Products

• VMware Data Services Manager for VCF

Issue/Introduction

When creating a default project and default namespace in VCF 9.1 the VCFA Quick Start wizard works as expected, creating a default project and default tenant org namespace for consumption. However, such a namespace may not be able to be used to deploy DBs in DSM.

In this situation the following error may be see:

"binding" not found

 

Environment

VCF 9.1 and Data Services Manager.

Cause

This namespace cannot be used to deploy DBs because DSM failed to create a corresponding namespace for VCFA namespace. DSM adds a random prefix to a VCFA namespace, and the ultimate name exceeds the 63 characters limit.

Resolution

Workaround: Don’t use the default namespace, create one.

This issue will be resolved in an upcoming version of VCF

Additional Information

DSM provider logs show:

{"level":"error","ts":"2026-03-19T23:54:28.436070513Z","logger":"controller.dataservicepolicybinding","msg":"Reconciler error","request":{"name":"default-namespace-#######-####-####-####-######"},"reconcileID":"#######-####-####-####-######","error":"failed to apply DSPolicyBinding: unable to create namespace on gateway: failed to create or upd
ate namespace #######-####-####-####-###### on gateway: Namespace \"#######-####-####-####-######" is invalid: [metadata.name: Invalid value: \"#######-####-####-####-######\": must be no more than 63 characters, metadata.labels: Invalid value: \"#######-####-####-####-######\": must be no more than 63 characters]","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controll
er[...]).