Stuck when patching ESXi using lifecycle

Products

• VMware vSphere ESXi

Issue/Introduction

• During patching ESXi, it shows that the host is rebooting and it lasts for a long time.

• In fact, ESXi has been rebooted and patched successfully.

 

• In vpxd.log, you can see the follow error:

yyyy-mm-ddThh:mm:ss warning vpxd[06033] [Originator@6876 sub=TrustedInfrastructure.HostConfig opID=HeartbeatStartHandler-27a64c1b-xxxxxxxx] [CreateOrUpdate] Policy with local user name vpxuser already exists on host <Host FQDN>. Exception: N4Vpxd7Clients22AlreadyExistsExceptionE(Error:
-->    com.vmware.vapi.std.errors.already_exists
--> No messages!
--> )
-->

[context]zKq7AVExxxxxxxxxxxxxxxx[/context]. Attempting update.
yyyy-mm-ddThh:mm:ss info vpxd[06033] [Originator@6876 sub=TrustedInfrastructure.HostConfig opID=HeartbeatStartHandler-27a64c1b-xxxxxxxx] [PolicyUpdater] Grants for client profile LU###vpxuser on host <Host FQDN> are already in desired state

yyyy-mm-ddThh:mm:ss warning vpxd[06033] [Originator@6876 sub=TrustedInfrastructure.HostConfig opID=HeartbeatStartHandler-27a64c1b-xxxxxxxx] [CreateOrUpdate] Policy with external group name TrustedAdmins already exists on host <Host FQDN>. Exception: N4Vpxd7Clients22AlreadyExistsExceptionE(Error:
-->    com.vmware.vapi.std.errors.already_exists
--> No messages!
--> )
-->

 

Environment

VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

Can not add ESXi to vCenter after disconnected during rebooting which results in vpxa agent service crash.

The host is disconnected from vCenter.

Therefore, the lifecycle cannot detect that ESXi has been rebooted successfully stuck in the patching.

 

 

Resolution

Restart the vpxa service and reconnect the ESXi to vCenter.