Back to bug 1850466
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Simon Pasquier | 2020-06-24 14:43:46 UTC | Target Release | 4.5.z | 4.5.0 |
| OpenShift BugZilla Robot | 2020-06-24 14:44:12 UTC | Status | ASSIGNED | POST |
| OpenShift BugZilla Robot | 2020-06-24 14:44:14 UTC | Link ID | Github openshift/cluster-monitoring-operator/pull/822 | |
| Simon Pasquier | 2020-06-24 14:50:24 UTC | Blocks | 1850615 | |
| OpenShift BugZilla Robot | 2020-06-24 15:52:44 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2020-06-24 19:17:45 UTC | Status | MODIFIED | ON_QA |
| Junqi Zhao | 2020-06-29 13:01:44 UTC | Status | ON_QA | VERIFIED |
| Simon Pasquier | 2020-07-06 12:59:26 UTC | Doc Text | Cause: the AlertmanagerConfigInconsistent alert could fire during an upgrade because some of the Alertmanager pods were temporarily not running due to a rolling update of the statefulset. The alert resolved itself once all Alertmanager pods had been updated. Consequence: the firing alert generated noise that was confusing for the cluster admins, especially because there wasn't any inconsistency in the configuration. Fix: the AlertmanagerConfigInconsistent alert has been fixed to not consider the number of running Alertmanager pods. Result: the AlertmanagerConfigInconsistent alert doesn't fire anymore during upgrades when some of the Alertmanager pods are in a not-running transient state. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2020-07-13 17:44:38 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-07-13 17:44:38 UTC | |||
| errata-xmlrpc | 2020-07-13 17:45:00 UTC | Link ID | Red Hat Product Errata RHBA-2020:2409 |
Back to bug 1850466