nagios-check falsely claims "Nagios not installed, or no nagios checks found"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On one of my CI jobs, nagios-check failed as follows:
2020-03-20 02:22:49 [ERROR] Nagios not installed, or no nagios checks found on ubuntu-mirror/1
2020-03-20 02:22:49 [ERROR] Nagios not installed, or no nagios checks found on ubuntu-mirror/0
I worked through the Nagios checks and they all exist and work, although not all of the succeed.
I checked the Mojo code, and the above is triggered by this:
if 'No such file or directory' in output or 'sudo: unknown user: nagios' in output:
and having reviewed my checks' output, it was triggered by this:
ubuntu@
stat: cannot stat '/srv/ftp.
I suggest the following:
* include "output" when reporting a problem
* separate the conditions above, and report them separately
* tighten up or change the "No such file or directory" check to problem it's intended to disagnose
Related branches
- Tom Haddon: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 40 lines (+9/-4)2 files modifiedmojo/phase.py (+5/-2)
mojo/tests/test_phase.py (+4/-2)
description: | updated |
Changed in mojo: | |
assignee: | nobody → Paul Collins (pjdc) |
Changed in mojo: | |
status: | New → Confirmed |
status: | Confirmed → Fix Committed |
Changed in mojo: | |
status: | Fix Committed → Fix Released |
Briefly assigned and unassigned, but the problem I just ran into is a different one with the same symptom.