When configuring TimeMonitor with multiple hosts the first results from ntpdate with a stratum above zero is chosen. However, that might not be the best result and not the server chosen by ntpdate.
If the (incorrectly) chosen server has an incorrect time but the other are fine, this could potentially be causing a false positive and set the state to OUT_OF_SYNC.
See below example where the TimeMonitor would use the second line of output for 18.104.22.168 while at the last line it can be seen that ntpdate instead chose 22.214.171.124:
- Change the logic in TimeMonitor to instead look at the last line with the format like "DATE ntpdate[PID] step time server HOST offset TIME sec".
- Write manuel test steps (text) for QA.