ptp-notification-armada-app/notificationservice-base/docker/ptptrackingfunction/trackingfunctionsdk/common/helpers
Cole Walker eb1e16685d Handle incomplete pmc results
Improve the logic for handling incomplete results when a pmc query
returns empty data.

There are intermittent instances where a pmc command returns an empty
result. The previous logic would result in ptp-notification considering
the ptp state to be in Freerun, but this could lead to undesirable
results where incorrect notifications are delivered.

This update allows ptp-notification to retry the pmc commands on the
next cycle and only updates the ptp status when the results are
complete. Additional logging has been added to indicate which pmc
results are missing.

Test plan:
Pass: Verify container image builds
Pass: Verify ptp-notification deployment
Pass: Verify basic operations (get, subscribe, list, delete)
Pass: Verify that ptp-notification does not deliver incorrect freerun
notifications when pmc results are incomplete
Pass: Verify that ptp-notification delivers a notification when ptp lock
is actually lost

Story: 2011056
Task: 51049

Signed-off-by: Cole Walker <cole.walker@windriver.com>
Change-Id: Ic473fcb44e16db629f12208e581a92abc3558480
2024-09-20 12:26:05 -04:00
..
constants.py Update default ptp4lClockClassLockedList values 2023-09-21 09:58:27 -04:00
log_helper.py Build Debian container image for notificationservice-base-v1-api 2023-01-30 15:05:15 +00:00
ptpsync.py Handle incomplete pmc results 2024-09-20 12:26:05 -04:00
rpc_helper.py Use new get_rpc_client API from oslo.messaging 2023-03-20 17:47:02 -03:00