NRPE check reports OK, but status is CRITICAL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NTP Charm |
New
|
Undecided
|
Unassigned |
Bug Description
Upgraded charm to master + build from the master of layer-ntpmon. On a host where no upstream servers can be reached, the check result was OK, but the text was accurate:
NRPE check reports OK, but status is CRITICAL: reachability is too low (0.00%) - must be greater than 50.00%
$ sudo chronyc sources
210 Number of sources = 20
MS Name/IP address Stratum Poll Reach LastRx Last sample
=======
^? b335.cxs.pw 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp3.torix.ca 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp1.exa-
^? time.cloudflare.com 3 10 0 62h -1478us[-1478us] +/- 94ms
^? time.videxio.net 0 10 0 - +0ns[ +0ns] +/- 0ns
^? berlix.fraho.eu 0 10 0 - +0ns[ +0ns] +/- 0ns
^? 196.49.6.106 0 10 0 - +0ns[ +0ns] +/- 0ns
^? 192.33.214.47 0 10 0 - +0ns[ +0ns] +/- 0ns
^? server2.
^? 220-133-
^? ntp02.maillink.ch 0 10 0 - +0ns[ +0ns] +/- 0ns
^? ntp4.inx.net.za 0 10 0 - +0ns[ +0ns] +/- 0ns
^? repository.
^? bwntp2pool.
^? ntp3.wirehive.net 0 10 0 - +0ns[ +0ns] +/- 0ns
^? uruz.org 0 10 0 - +0ns[ +0ns] +/- 0ns
^? chilipepper.
^? alphyn.
^? golem.canonical.com 0 10 0 - +0ns[ +0ns] +/- 0ns
^? pugot.canonical.com 0 10 0 - +0ns[ +0ns] +/- 0ns