Understanding Namespace Import Limitations in VCF Automation 9.1

Products

• VCF Automation

Issue/Introduction

Following a restore of VCF Automation (VCFA), users may find that namespaces and projects created after the backup of the VCFA, are orphaned and no longer linked to the VCFA organization. Attempts to re-map these namespaces using the API namespace import call fail with the following error:

Error Code: "BAD_REQUEST", "message": "Namespace import is not supported for a supervisor associated with NSX Manager".

Additionally, virtual machines associated with these orphaned namespaces may be locked in a "supervisor managed" state, preventing standard manual movement or migration due to permission denial.

Environment

VCF Automation 9.1

Cause

The namespace import feature in VCF Automation 9.1 is not a universal recovery tool for post-restore synchronization. It is architecturally scoped to support only a legacy subset of namespaces (primarily version 8.0.3).

Objects created after a point-in-time backup do not exist in the restored VCFA database metadata. The API explicitly rejects the import action when the supervisor is associated with an NSX Manager, which is the standard configuration in modern VCF environments.

Resolution

The supported method to restore environment functionality for orphaned objects is to manually re-create the necessary namespaces and projects within the post-restore VCFA environment.

Additional Information

It is recommended that users subscribe to the related KB Article to be updated on any future changes to feature supportability.