NTP Charm

Frequent, self-resolving alerts for "No sync peer selected"

Bug #1905332 reported by Xav Paice
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
NTP Charm
Fix Released
Undecided
Unassigned

Bug Description

On several clouds we are receiving alerts noting "No sync peer selected", however these resolve by the time we connect and go to look to find out what's happening. The check should probably be made less sensitive, or at least some detail logging left somewhere so we have a clue what to look for to prevent these alerts.

Tags: iso-testing
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1905332

tags: added: iso-testing
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Upstream has denied the feature request, as a configurable timeframe for sync peer change would require holding state between checks, and the product is not developed to allow measuring such.

The suggestion upstream is to migrating to Alertmanager which allows for customized time-series based alert thresholds.

https://github.com/paulgear/ntpmon/issues/6
https://github.com/paulgear/ntpmon/pull/10#issuecomment-703838535

To help address this, the charm has also had max_check_attempts configuration added to allow for ignoring a critical state for longer than the default 4 minutes. Some configurations we've found that mitigate the sync peer check noise are max_check_attempts=8 or max_check_attempts=12.

Changed in ntp-charm:
status: New → Fix Released
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Marked fix-released as max_check_attempts is an available solution for this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.