Lifecycle Manager compliance check times out

Products

• VMware vSphere ESXi

Issue/Introduction

• Lifecycle Manager compliance check times out
• Lifecycle Manager ESXi host updates times out
• /var/log/vmware/vmware-vpxd/vpxd.log shows output that appears to exceed the character limit
  

  [timestamp] error vpxd[06787] [Originator@6876 sub=Default opID=[opID] [VpxLRO] -- [Session ID] -- EsxHostAdvSettings-431 -- vim.option.OptionManager.queryView: :vim.fault.InvalidName
  --> Result:
  --> (vim.fault.InvalidName) {
  -->    faultCause = (vmodl.MethodFault) null,
  -->    faultMessage = <unset>,
  -->    name = "UserVars.ImageCachedSystem",
  -->    entity = <unset>
  -->    msg = "Received SOAP response fault from [<<io_obj p:0x00007f47781877a8, h:157, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-431/vpxa>]: queryView
  --> Received SOAP response fault from [<<io_obj p:0x0000006a80056768, h:19, <TCP '127.0.0.1 : 31588'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: queryView
  --> 'UserVars.ImageCachedSystem' is invalid or exceeds the maximum number of characters permitted."
  --> }
  --> Args:
  -->
  --> Arg name:
  --> "UserVars.ImageCachedSystem"

Cause

The python logger in esxupdate file is unable to handle large size input , specifically > 16Kib . This is causing the vum staging or compliance check to get stuck, as the viburl size that is passed as argument is ~20Kib in size. To address this, esxupdate now prints the options argument in chunks to ensure the python logging doesn't get stuck.

Resolution

This issue is fixed in ESXi 7.0 Update 3c or later.

The workaround is comment out line "logger.info('---\nCommand: %s\nArgs: %s\nOptions: %s' % (command, args, options))" of /bin/esxupdate file.