Service VM not powering on after deployment

Products

• VMware NSX-T Data Center
• VMware NSX

Issue/Introduction

• Below error is seen while powering on the VM from vCenter: "vim.fault.InsufficientAgentVmsDeployed"
• Service redeployment in the NSX manager would show up as in progress.
• Following events are reported in the proton-tomcat-wrapper log on the NSX managers: 

/var/log/proton/proton-tomcat-wrapper.log: 

INFO | jvm 1 | YYYY/MM/DD HH:MM:SS | "EamPollingThread" #1314 daemon prio=5 os_prio=0 tid=0x0000006621d37800 nid=0x3a50 runnable [0x000003a4ebf01000]
INFO | jvm 1 | YYYY/MM/DD HH:MM:SS | java.lang.Thread.State: RUNNABLE
INFO | jvm 1 | YYYY/MM/DD HH:MM:SS | at java.net.SocketInputStream.socketRead0(Native Method)

Environment

VMware NSX

Cause

The EamPollingThread is getting stuck indefinitely while waiting for a response.

Resolution

This issue is resolved in NSX-T 3.1.0 and higher.

 

Workaround:

• Restart proton service on the NSX manager by running the following CLI command as Root user:
  • /etc/init.d/proton restart
• To check the status of the service after restart, please run the command:
  
  • /etc/init.d/proton status

Additional Information

Impact/Risks: Unable to power on any VM's on the affected host and the guest introspection service VM (GI SVM) is not available after a redeployment of the VM. The status in the NSX-T manager will be stuck as "in-progress."