Unable to create transport node collection with profile ###-###-###-###-### on compute collection XYZ through nsxmanager nsxmanager1
"level="ERROR" errorCode="MPA12104"] Failed to get vmk state info for dvs <dvsname>
"Error in acquiring resource locks Resource with type HOST, and ID <UUID> or Name null is not found."
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware NSX
The Compute Manager has not synced correctly for some time with NSX and fails to pull the needed information for the SDDC task to complete successfully.
This is a condition that may occur in a VMware NSX environment.
Workaround
Note: If you have both Validation errors, and SDDC Task failures (Failed to Acquire Resource Locks, Unable to create transport node collection with profile) apply both options below:
Option 1:
The workaround involves resyncing Compute manager within NSX.
Note:
The workaround involves re-registering even if it shows that its currently in sync with Compute manager within NSX.
Run steps below through NSX UI to resolve:
Option 2:
The workaround involves detaching and reading the TNP to hosts with the Validation errors in the NSX UI.
Note:
Need to put each host in MM before detaching the TNP and re-attaching.
Note: If TNP is applied to the cluster, should only need to select the radio option next to the cluster level, detach TNP from the cluster, and reattach after putting the Hosts with Validation errors in MM.