Resolving NTA Server and llanta Pod Errors Post TKG 1.22.9 Upgrade in NAPP 4.1.1

Products

• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

Symptoms:

• Following an upgrade, the nta-server is displaying an error message. The llanta pod is also exhibiting a crash loopback status.
• After the NSX Application Platform upgrade, nta-server logs are showing the error: "Exception Processing ErrorPage[errorCode=0, location=/error]".

This can be observed in the console log using kubectl <options> logs nta-server or in the support bundle at var/log/napp/supportbundle/nsxi-platform/k8sworker*/nta-server.log

• The llanta pod is in a crash loopback state.
• Relavent Log Location : Pod logs from nta-server and llanta pod. Search for the above mentioned error message mentioned

 e.g., kubectl <kubeconfig> logs <nta-server-pod-name>.

 

Environment

VMware NSX 4.1.0

 

Cause

Not Applicable/Yet to be determined

Resolution

Not available yet.

Workaround:
Restart the nta-server pod using one of the following commands:

• kubectl <kubeconfig> delete pod <nta-server-pod-name>
• kubectl <kubeconfig> rollout restart deployment nta-server

After restarting, ensure that the previously documented error does not reappear and that the nta-server pod is in a running state.

• Note: A failed liveness probe indicates pod failure.

Additional Information

Impact/Risks:
The NTA detection page displays an error banner, indicating that NTA functionality is impaired post-upgrade.