
Three fixes: 1. Handle a case where the ptp_montor would fail if ptp4l/phc2sys were restarted while ptp-notification is running 2. Correct the logic for determining if the local node is a GM. There was a case where the node was declared a GM if the upstream GM went down, even though local ports were configured not to become master. 3. Correct an issue where the ptp sync state was not set properly on startup and could not transition out of Freerun Test plan: PASS: Build and deploy new container image PASS: PTP state reaches freerun when upstream GM goes down PASS: ptp-notification continues running and resumes monitoring ptp4l state after ptp4l/phc2sys service restart on host Story: 2010056 Task: 46376 Task: 46377 Task: 46378 Signed-off-by: Cole Walker <cole.walker@windriver.com> Change-Id: I3ac29fc56f9e72efc5b6ef02fa5472d9d801fbb7
Description
StarlingX PTP Notification App
Languages
Python
97%
Makefile
1.2%
Dockerfile
0.6%
Shell
0.4%
Smarty
0.3%
Other
0.4%