The EDAA operations on notification fails

The EDAA operations on notifications like Acknowledge, UnAcknowlege, Browse Details, and Containment fails, even though the EDAA and SAM Presentation server is up and running.

Root Cause

The SAM configuration from a DM adapter is getting deleted because of which EDAA operations in VMware Telco Cloud Service Assurance are failing with 404 error.

Solution

Run the following command inside any of the pod running in a Kubernetes cluster:

1. To log in to POD, execute the following command in any of Node of a Kubernetes cluster:

   kubectl exec -it <POD NAME> bash

2. To verify the Routes in a DM adapter, run the following command inside the pod:

   curl --location --request GET 'http://dm-adapter:9999/actuator/gateway/routes'

3. If routes returned are empty, then run the following command to refresh the routes

   curl --location --request POST 'http://dm-adapter:9999/actuator/gateway/refresh'