VMware vCenter Server
This issue is typically caused by stale or incomplete plugin registration within the vCenter Server. This may occur if the plugin registration in the Managed Object Browser (MOB) does not match the cached data in the vSphere UI Serenity database, or if the user account associated with the plugin lacks sufficient permissions (e.g., Read-Only instead of Administrator) to complete the installation and backend connection.
Follow these steps to perform a teardown and purge the plugin cache to allow for a clean re-registration:
Prerequisites
Procedure
service-control --stop vsphere-uicd /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenityrm -rf <plugin_folder_name>NOTE: Ensure the service account used for the vCenter target in Intersight has Administrator level privileges to ensure the plugin can register and communicate with the backend services.