TLS 1.1 check is weird
Bug #1879608 reported by
Paul Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Content Cache Charm |
Fix Released
|
Medium
|
Haw Loeung | ||
Bug Description
The TLS 1.1 check's message when it's OK is "CRITICAL - Cannot make SSL connection.", which is weird and confusing.
Also confusing is why this isn't implemented in tlsmon.
Related branches
~hloeung/content-cache-charm:nagios-monitoring
- Paul Collins: Approve (lgtm)
- Canonical IS Reviewers: Pending requested
-
Diff: 106 lines (+1/-62)2 files modifiedreactive/content_cache.py (+1/-26)
tests/unit/test_content_cache.py (+0/-36)
Revision history for this message
| Haw Loeung (hloeung) wrote | #1 |
| Changed in content-cache-charm: | |
| status: | New → In Progress |
| assignee: | nobody → Haw Loeung (hloeung) |
| Changed in content-cache-charm: | |
| status: | In Progress → Fix Committed |
| importance: | Undecided → Low |
| importance: | Low → Medium |
| Changed in content-cache-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Agreed. It's certainly caught me by surprise seeing mojo run with all these CRITCALs because it's using the 'negate' NRPE plugin.
FWIW, the current configs makes disabling SSLv3/TLS1.0/TLS1.1 global. So one check for this should be enough rather than one check per site (so on a setup with over 100 sites, that's a lot of extra checks).
Also, as mentioned, this should be handled by tlsmon.