NRPE check_replica_sets in 21.01 mongodb charm shows CRITICAL on single unit mongo deployment
Bug #1914080 reported by
Drew Freiberger
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MongoDB Charm |
Fix Released
|
Medium
|
Chris Johnston |
Bug Description
I'm noticing two issues with the newly added check_replica_sets nrpe monitor for mongodb:
1. the check is named check_check_
2. The check should not be enabled on single-node mongodb installations (like in single-node graylog + mongodb setups)
Related branches
~cjohnston/charm-mongodb:lp-1914080
- Adam Dyess (community): Approve
- Paul Goins: Approve
- BootStack Reviewers: Pending requested
-
Diff: 210 lines (+114/-12)6 files modifiedhooks/hooks.py (+12/-7)
tests/functional/tests/bundles/bionic-replicated.yaml (+18/-0)
tests/functional/tests/bundles/bionic.yaml (+11/-1)
tests/functional/tests/bundles/focal.yaml (+11/-1)
tests/functional/tests/tests.yaml (+11/-1)
tests/functional/tests/tests_mongodb.py (+51/-2)
~cjohnston/charm-mongodb:fix-check-replicaset-name
- Xav Paice (community): Approve
- Adam Dyess (community): Approve
- BootStack Reviewers: Pending requested
-
Diff: 16 lines (+2/-1)1 file modifiedhooks/hooks.py (+2/-1)
Changed in charm-mongodb: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in charm-mongodb: | |
assignee: | nobody → Chris Johnston (cjohnston) |
status: | Triaged → Fix Committed |
Changed in charm-mongodb: | |
milestone: | none → 21.10 |
Changed in charm-mongodb: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
On a single-node mongo install the nagios alert is:
CRITIAL: unable to determine the replica set name