Summary: | 4.1 etcd clusters are reporting a down "etcd" service, but no alert is firing on the cluster | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
Component: | Etcd | Assignee: | Clayton Coleman <ccoleman> |
Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.z | CC: | mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.1.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-15 14:24:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Bug Depends On: | 1734540 | ||
Bug Blocks: |
Description
Clayton Coleman
2019-07-16 16:01:07 UTC
Ok, looking into this we have a gap in our alerts. Today we have etcdInsufficientMembers which depends on the etcd service being present but down (we must have 3 up series). However, when this happens we only fire TargetDown and that's concerning since we're really degraded. We need to have a better alert for degradation Second, there is a different failure mode where a node is completely removed, at which point the number of series in up is 2, and the alerts do not fire correctly. This is a valid failure mode that our alerts don't cover. The query `count(sum by (To) (rate(etcd_network_peer_sent_failures_total[2m])) > 0) > 0` roughly approximates this. Verfied with 4.1.0-0.nightly-2019-08-06-212225, shutdown 1 etcd member, then check Monitoring section in web console, got expected alert msg: etcdMembersDown etcd cluster "etcd": members are down (1). Pending Since 2 minutes ago Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2417 |