Remediation of ESXi host via vSphere Lifecycle Manager (vLCM) times out

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

• Remediation of ESXi host via vSphere Lifecycle Manager (vLCM) times out. 

Logs on the vCenter server : /var/log/vmware/vmware-updatemgr/vmware-vum-server.log 

<timestamp> warning vmware-vum-server[3194427] [Originator@6876 sub=RecommendationEngine::ImageMgrSubsystem] [imageMgrSubsystem 185] Software Spec validation failed with results {
-->     "errors": [
-->         {
-->             "id": "com.vmware.vcIntegrity.lifecycle.Validate.Depend",
-->             "message": {
-->                 "args": [
.
.
.
-->                 "default_message": "Component {1} has unmet dependency {2}. It depends on one of the following: {3}.",

• The host is configured with an image from one vendor (here, Dell), but the additional components that have been added are from another vendor (here, Cisco)
  
  /var/log/vmware/vmware-updatemgr/vmware-vum-server.log 

<timestamp> info vmware-vum-server[3194427] [Originator@6876 sub=RecommendationEngine::ImageMgrSubsystem] [imageMgrSubsystem 126] SoftwareSpec: {
-->     "add_on": {
-->         "name": "DEL-ESXi-703",
-->         "version": "23794027-A23"
-->     },
-->     "alternative_images": null,
-->     "base_image": {
-->         "version": "7.0.3-0.125.23794027"
-->     },
-->     "components": {
-->         "Cisco-nenic": "2.0.11.0-1OEM.800.1.0.20143090",
-->         "Cisco-nfnic": "5.0.0.44-1OEM.800.1.0.20613240",
-->         "Intel-Volume-Mgmt-Device": "3.5.1.1002-1OEM.800.1.0.20613240",
-->         "Mellanox-nmlx4": "3.19.70.2001-1OEM.700.1.0.15843807",
-->         "Microchip-smartpqi": "80.4700.0.5000-2vmw.803.0.0.24022510",
-->         "Pensando-ionic-en": "20.0.0-49vmw.802.0.0.22380479"
-->     },
-->     "hardware_support": null,
-->     "removed_components": null,
-->     "solutions": null
--> } before its validate.

Environment

VMware vSphere ESXi 7.x 
VMware vSphere ESXi 8.x
VMware vSphere vCenter Server 7.x 
VMware vSphere vCenter Server 8.x 

 

Cause

The issue is caused due to incorrect vendor components added to the cluster image SoftwareSpec. 

 

 

Resolution

Remove the opposing vendor components from the SoftwareSpec. 

• Put the ESXi host in maintenance mode
• Log in to the ESXi host via SSH. 
• Validate the VIBs on the host specific to the opposing vendor using the below command - 

esxcli software vib list 

• Remove the VIB below command:

esxcli software vib remove --vibname= <vib_name>

• Reboot the ESXi Host

Additional Information

Edit an Image (7.0) 

Working with Images (8.0)