4efcb548dbe7257a5ad22fc1903c555fc47f3a6b
When no ts2phc instance is configured on a node, collectd incorrectly tries to check 'clock' type instances for a PTP lock state. The 'clock' instance type does not contain ptp4l configuration info and should not be part of this check. This was resulting in an incorrect 'ptp no-lock' alarm being raised. Updated the logic for calling check_ptp_regular() so that 'clock' instances are excluded. Test plan: PASS: Configure system with clock instance and no ts2phc instance, verify alarm is not raised. PASS: Configure system with clock and ts2phc instances and verify that normal behaviour is unaffected. Closes-bug: 1998132 Signed-off-by: Cole Walker <cole.walker@windriver.com> Change-Id: Id3941ed2079478e9c1241cf613d3fa3486e653c0
Description
StarlingX system monitoring and repoting tools
Languages
Python
85.9%
Perl
12.9%
Makefile
1%
Shell
0.2%