VUM plugin mismatch between the Managed Object Browser (MOB) and plugin directory

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• The version of the VMware Update Manager (VUM) plugin in the vCenter Managed Object Browser (MOB) - https://vcsa.vsphere.local/mob/?moid=ExtensionManager&doPath=extensionList%5b"com.vmware.vcIntegrity"%5d - is different from what is available in the file system of the VCSA in the HTML5 client or Flex Client (Flash).
  • HTML5 Client

/etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/

• Flex Client (Flash)

 /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/ 

 

Environment

VMware vCenter Update Manager 6.7.x

Resolution

Note: Before applying the steps below, please ensure to take a backup or an offline snapshot of the VCSA. If the VCSA is a member of a Linked Mode replication group, please ensure to have backups or offline snapshots of all of its replication partners as well.

1. Open an SSH connection to the vCSA and log in with the root account
2. Download the plug-ins
   1. for HTML5 client:

      # curl https://<vCenterFQDN>:9087/vci/downloads/vum-htmlclient.zip --insecure >/etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vum-htmlclient.zip

   2. for vSphere Flex Client:

      # curl https://<vCenterFQDN>:9087/vci/downloads/vumclient.zip --insecure >/etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vumclient.zip

3. Create two folders with the same version as listed in the vCenter MOB:

   # mkdir /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vum.client-6.7.0.42050
   
   # mkdir /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.42050

4. Unzip the content of the two packages in the new folders:

   # unzip /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vum-htmlclient.zip -d /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vum.client-6.7.0.42050
   
   # unzip /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vumclient.zip -d /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.42050

5. Change the permissions on the two folders:

   # chmod -R 755 /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vum.client-6.7.0.42050
   
   # chmod -R 755 /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.42050

6. Change the ownership for both folders:

   # chown -R vsphere-ui:users /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vum.client-6.7.0.42050
   
   # chown -R vsphere-client:users /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.vcIntegrity.vcIntegrity-6.7.0.42050

7. Delete the .zip archives:

   # rm /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vum-htmlclient.zip
   
   # rm /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin/vumclient.zip

8. Restart both client services:

   # service-control --restart vsphere-ui
   
   # service-control --restart vsphere-client

9. Login to both clients and verify that the issue no longer occurs