DX NetOps Flow Analytics Installation Fails with ResourceAccessException

Products

• Network Observability

Issue/Introduction

Check flow inventory logs using below command

kubectl logs flow-inventory-lookup-xxxx-xxxx-vm -n default   -c flow-inventory-init   --previous

 [flow-inventory-init] [           main] o.s.boot.SpringApplication               : Application run failed

java.lang.IllegalStateException: Failed to execute CommandLineRunner

Caused by: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://DA:8582/rest/flow/protocolnames": da.simac.be: Name or service not known

Caused by: com.broadcom.netops.flow.common.commons.exception.FlowException: Error retrieving protocol names

Environment

• Product: DX NetOps Flow Analytics 25.4.5
• Infrastructure: Kubernetes / RKE2

Cause

Stale "no-DNAT" conntrack entries in the Linux kernel can black-hole traffic if packets arrive before the kube-proxy rules are fully initialized.

Resolution

Perform a helm upgrade using the same parameters

or 

full helm uninstall followed by a fresh helm install.

This ensures the application state is cleared and any stale conntrack entries are flushed.