Cluster Images Showing as Incompatible Without Further Detail
search cancel

Cluster Images Showing as Incompatible Without Further Detail

book

Article ID: 452012

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Hosts are showing as Incompatible when running compliance checks within vSphere Cluster LCM. No details such as expected lists of incompatible VIBs are shown: 

Environment

vCenter Server 8.0 U3
vSphere Replication 9.0.2

Cause

A lower version of the vmware-hbr-agent Solution VIB for vSphere Replication is being pushed to ESXi hosts through vCenter automatically than what is included in the Cluster Image. This VIB is classified as a Solution which is why it does not show in a list of "outdated VIBs" such as the example output below: 

Resolution

  1. SSH into vSphere Replication Nodes as Root.
  2. Set the HBR vib auto-push to False to stop automatic pushing of the VIB to hosts.
    • /opt/vmware/hms/bin/hms-configtool -cmd reconfig -property hms-auto-install-hbragent-vib=false
  3. Restart the HMS service 
    • service hms restart
  4. SSH into each effected host and remove the vmware-hbr-agent vib  

    (Note: vSphere Replication will not be effected. This change is reverted later.)

    • esxcli software remove -n vmware-hbr-agent
  5. Re-run compliance check on the cluster. If successful - Remediate.
  6. Cleanup steps: 
    1. SSH to vSphere Replication Nodes as Root.
    2. Run the following commands to re-enable hbr VIB auto-push: 
      1. /opt/vmware/hms/bin/hms-configtool -cmd reconfig -property hms-auto-install-hbragent-vib=true
      2. service hms restart

Additional Information

vSphere Lifecycle management (vLCM) support for vSphere Replication