VxRail Plugin Registration Fails with SecurityError After Upgrade
search cancel

VxRail Plugin Registration Fails with SecurityError After Upgrade

book

Article ID: 439677

calendar_today

Updated On:

Products

VMware vRealize Automation 8.x

Issue/Introduction

After an upgrade or re-deployment of VxRail Manager, the VxRail plugin fails to register or operate correctly within the vCenter UI.

Although the com.dell.vxrail extension may appear to be missing from the vCenter Managed Object Browser (MOB) ExtensionList, querying the extension via FindExtension still returns a result, indicating a stale or corrupt registry state.

Symptoms:

  • VxRail Manager is not visible in the vSphere Client.

  • Attempts to re-deploy or register the plugin fail with a 500 error.

  • The following error messages are observed in the vCenter logs:

File: /var/log/vmware/envoy/envoy-access.log

Plaintext
 
POST /sdk 500 via_upstream - ... "RegisterExtension"

File: /var/log/vmware/vpxd/vpxd.log

Plaintext
 
error vpxd[...] [Originator@6876 sub=Default opID=...] [VpxLRO] -- ERROR lro-... -- ... -- ExtensionManager -- vim.ExtensionManager.registerExtension: :vmodl.fault.SecurityError
--> url = "https://<VxRail_IP>/plugin.json"

Environment

 

  • VMware Aria Automation (formerly vRealize Automation)

  • VxRail Manager

  • vCenter Server 7.x / 8.x

 

Cause

The issue is caused by corruption in the vCenter Lookup Service extension registry. Stale plugin data and conflicting extension entries (specifically com.vmware.vxrail vs com.dell.vxrail) remain in the vCenter file system and database.

This causes a SecurityError (Access Denied) when the Extension Manager attempts to overwrite or create new registry entries during the plugin registration process.

Resolution

To resolve this issue, you must manually clean up the stale extension files and re-register the plugin. When the vxrail extension is already unregistered.

  1. Log in to the vCenter Server Appliance (VCSA) via SSH as root.

  2. Navigate to the cmCatalog directory and remove the stale VxRail zip file:

    rm -rf /etc/vmware/vsphere-ui/cmCatalog/com.vmware.cis.com.dell.vxrail.zip
    
  3. Clean up the stale extension entries located in the extensions directory:

    • Check /etc/vmware-vpx/extensions/ for any files related to com.vmware.vxrail and com.dell.vxrail and remove them.

    • Note: For detailed steps on removing extensions from the MOB, refer to Broadcom KB 396101.

  4. Restart all vCenter services to clear the cache and reload the registry:

    Bash
     
    service-control --stop --all
    service-control --start --all
    
  5. Retry the VxRail plugin registration from the VxRail Manage