| 2022-10-05 13:21:42 |
Douglas Henrique Koerich |
description |
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. |
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
--------------
Before moving the server, returned 200 OK:
2022-10-03T13:16:45.762801209Z stdout F 2022-10-03 13:16:45,762 [DEBUG ] [notificationclientsdk.client.base][MainThread] Created Broker client:controller-1,rabbit://admin:admin@[172.16.166.133]:5672672]:5672
2022-10-03T13:16:45.936465044Z stdout F 2022-10-03 13:16:45,935 [INFO ] [pecan.commands.serve][MainThread] "GET /ocloudNotifications/v1/PTP/CurrentState HTTP/1.1" 200 169
Server moves:
2022-10-03T17:14:58.038412664Z stdout F 2022-10-03 17:14:58,038 [DEBUG ] [notificationclientsdk.services.notification_worker][MainThread] consume location info @controller-0:{'NodeName': 'controller-0', 'PodIP': '172.16.192.65', 'ResourceTypes': ['PTP'], 'Timestamp': 1664817297.893791}
After moved, returned 404 Not Found:
2022-10-03T17:21:27.099411681Z stdout F 2022-10-03 17:21:27,098 [DEBUG ] [notificationclientsdk.client.base][MainThread] Created Broker client:controller-1,rabbit://admin:admin@[172.16.166.133]:5672
2022-10-03T17:21:46.127691768Z stdout F 2022-10-03 17:21:46,126 [WARNING ] [pecan.commands.serve][MainThread] "GET /ocloudNotifications/v1/PTP/CurrentState HTTP/1.1" 404 62
Test Activity
-------------
Feature Testing
Workaround
----------
Should move sidecar to the host where the server is currently running |
|
