NSX-V VIB install fails with EAM error code: 99
search cancel

NSX-V VIB install fails with EAM error code: 99

book

Article ID: 314274

calendar_today

Updated On:

Products

VMware NSX VMware vCenter Server 7.0

Issue/Introduction

  • You are using NSX for vSphere and vCenter Server 7.0u3
  • NSX VIB installation fails with UI error:
Agent VIB module cannot be detected on the host. This may be due to a pending reboot on the host due to an earlier operation, or the host may not be of supported version (Please check VMware Product Interoperability Matrices). Please check for any errors on the vCenter console or host that may be causing this. Resolving this error will attempt to install the VIB on the host again. 
  • Checking eam/mob the agent is created for the host
  • In var/log/vmware/eam/eam.log we can see an error for the host stating "error code: 99" 

2021-11-23T09:12:24.649Z | ERROR | host-12345 | VibJob.java | 465 | PatchManager operation failed with error code: 99 

  • Further down in eam.log we can see the Error Description as "Expected 1 component, found 2"

2021-11-23T09:12:24.682Z | ERROR | host-agent-2 | AuditedJob.java | 106 | JOB FAILED: [#629669248] InstallHostAgentJob(HostAgent(ID:

'Agent:########-####-####-####-############:null'))

com.vmware.eam.EamAppException: Could not complete AgentWorkflowJob because of[

eam.issue.VibNotInstalled {

  description = '<error errorClass="ValueError">

 <errorCode>99</errorCode>

 <errorDesc>Expected 1 component, found 2</errorDesc>

</error>',
 

NOTE: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.

Environment

NSX for vSphere

vCenter Server 7.0u3

 

Cause

  • Starting with vSphere 7.0 Update 3, the inbox i40enu network driver for ESXi changes name back to i40en
  • Grepping for the "i40" VIB on the effected host 2 are present - # esxcli software vib list | grep i40
    • i40en
    • i40enu
  • The VIB installation fails as EAM is expecting 1 driver however 2 drivers are present

Resolution

Currently there is no resolution to this issue

Workaround:

Manually remove the i40enu VIB from the host and restart EAM

#esxcli software vib remove -n i40enu
#service-control --restart vmware-eam 

VIB should install correctly on host