Comment 0 for bug 1991793

Brief Description
-----------------
After ptp-notification pod changes from one host to another, a running vDU sidecar starts to fail with 404 Not Found when pulling states (https://docs.starlingx.io/api-ref/ptp-notification-armada-app/api_ptp_notifications_definition_v1.html#pull-status-notifications)

Severity
--------
Major

Steps to Reproduce
------------------
- Set label "ptp-notification=true" to controller-1;
- Apply ptp-notification and install a pod with sidecar;
- Check pull status is working;
- Move label "ptp-notification=true" to controller-0, the ptp-notification pod is expected to move as well;
- From sidecar still running in the pod at controller-1, try pulling status again;
- /ocloudNotifications/v1/.../CurrentState will return "404 Not Found"

Expected Behavior
------------------
Sidecar should reach the API server running in another host

Actual Behavior
----------------
Sidecar only reaches the API server running in the same host the sidecar is installed

Reproducibility
---------------
Reproducible

System Configuration
--------------------
All except AIO-SX

Last Pass
---------
This is a new test scenario

Timestamp/Logs
--------------
Attach the logs for debugging (use attachments in Launchpad or for large collect files use: https://files.starlingx.kube.cengn.ca/)
Provide a snippet of logs here and the timestamp when issue was seen.
Please indicate the unique identifier in the logs to highlight the problem

Test Activity
-------------
Feature Testing

Workaround
----------
Should move sidecar to the host where the server is currently running.