We had the same issue and we had the same problem. Most notably that the vCLS systems were orphaned in the vCenter inventory, and the administrator@vsphere.local account had "No Permission" to resol...
See more...
We had the same issue and we had the same problem. Most notably that the vCLS systems were orphaned in the vCenter inventory, and the administrator@vsphere.local account had "No Permission" to resolve the issue from the vCenter DCLI. (Which is disturbing, given that even the owner of the system can't resolve issues with the vCLS systems.) We tried: - deleting he vCLS systems from storage (they were already orphaned) - deleting them using the dcli on the vCenter itself (no permission for the administrator@vsphere.local account - which is an affront to the natural order of the Universe) - Enabling Retreat Mode (setting the Advanced Settings for the specific cluster, disabling the vCLS feature, rebooting the vCenter, then enabling the vCLS mode) The ONLY thing that worked is the KBB above. NOTE: That KBB will generate MANY error even then it works.
