An administrator has been tasked with the deletion of a workload domain within a VMware Cloud Foundation (VCF) instance. The following information has been provided: - There are two workload domains…

Question

Options

• AThe NSX Edge Cluster Deployment Removal Tool was run against the workload domain.
• BThe NSX Edge cluster for the workload domain was deleted using NSX Manager.
• CThe NSX Manager is shared between the workload domains.
• DThe Network Pools associated with the workload domain were deleted using the vSphere client.

• A
  4% (1)
• B
  77% (20)
• C
  8% (2)
• D
  12% (3)

Explanation

In VMware Cloud Foundation, deletion of a workload domain requires that VCF Operations can correctly discover and process the NSX components attached to that domain. The workload domain delete workflow explicitly includes removal of the NSX Manager and NSX Edge components associated with the domain, unless those NSX components are shared. In earlier and current VCF guidance, VMware state that NSX Edge clusters for a workload domain must be removed using the documented/VCF-aware method (for example, using the NSX Edge removal process referenced in KB 78635, not by deleting objects directly in NSX Manager). If an administrator deletes the NSX Edge cluster directly in NSX Manager, the VCF inventory and orchestration logic still "believes" the Edge cluster exists. When the workload domain delete workflow reaches the stage "Gather input for deletion of NSX component", it queries NSX / internal state for Edge cluster data. Because the underlying object has been manually removed, the returned structure is null, which results in an internal "Cannot read the array length because "<locall9>" is null" style error.

No community discussion yet for this question.