Back to bug 2078611
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2022-04-25 19:26:55 UTC | Pool ID | sst_high_availability_rhel_8 | |
| Red Hat One Jira (issues.redhat.com) | 2022-04-25 19:34:48 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-119887 | |
| Ken Gaillot | 2022-04-25 19:40:02 UTC | Doc Text | Feature: Pacemaker alerts and alert recipients now support an "enabled" meta-attribute (defaulting to true) that can be set to false to temporarily disable the alert (as a whole or to the one recipient). Reason: During planned maintenance, there can be a lot of resource activity that the usual alert recipients don't need to worry about. Result: Alerts can now be disabled for any reason, such as planned maintenance. | |
| Keywords | Triaged | |||
| Target Release | --- | 8.8 | ||
| Type | Bug | Feature Request | ||
| Tomas Jelinek | 2022-04-27 08:40:51 UTC | Blocks | 2078265 | |
| Depends On | 2078265 | |||
| Arslan | 2022-04-29 02:30:19 UTC | Link ID | Red Hat Knowledge Base (Solution) 6955674 | |
| Ken Gaillot | 2023-01-12 20:26:00 UTC | Status | NEW | ASSIGNED |
| Target Release | 8.8 | 8.9 | ||
| Assignee | kgaillot | nrwahl | ||
| Reid Wahl | 2023-01-12 20:27:28 UTC | CC | nwahl | |
| Assignee | nrwahl | nwahl | ||
| Reid Wahl | 2023-03-16 21:16:44 UTC | Status | ASSIGNED | POST |
| Dean Jansa | 2023-05-16 13:10:43 UTC | CC | jrehova | |
| Link ID | Red Hat Issue Tracker CLUSTERQE-6694 | |||
| Chris Lumens | 2023-05-26 13:33:14 UTC | Fixed In Version | pacemaker-2.1.6-1.el8 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-05-26 13:39:51 UTC | Status | MODIFIED | ON_QA |
| Red Hat Bugzilla | 2023-08-10 15:41:12 UTC | Status | ON_QA | VERIFIED |
| CC | cluster-qe | |||
| QA Contact | cluster-qe | cluster-qe | ||
| Steven J. Levine | 2023-08-15 21:11:28 UTC | CC | slevine | |
| Doc Text | Feature: Pacemaker alerts and alert recipients now support an "enabled" meta-attribute (defaulting to true) that can be set to false to temporarily disable the alert (as a whole or to the one recipient). Reason: During planned maintenance, there can be a lot of resource activity that the usual alert recipients don't need to worry about. Result: Alerts can now be disabled for any reason, such as planned maintenance. | .New `enabled` alert meta option to disable a Pacemaker alert Pacemaker alerts and alert recipients now support an `enabled` meta option. Setting this option to `false` for an alert disables the alert. Setting this option to `true` for an alert and `false` for a particular recipient disables the alert for that recipient. The default value for this optio is `true`. You can use this option to temporarily disable an alert for any reason, such as planned maintenance. | ||
| Flags | needinfo?(kgaillot) | |||
| Ken Gaillot | 2023-08-15 22:27:23 UTC | Flags | needinfo?(kgaillot) | |
| Doc Text | .New `enabled` alert meta option to disable a Pacemaker alert Pacemaker alerts and alert recipients now support an `enabled` meta option. Setting this option to `false` for an alert disables the alert. Setting this option to `true` for an alert and `false` for a particular recipient disables the alert for that recipient. The default value for this optio is `true`. You can use this option to temporarily disable an alert for any reason, such as planned maintenance. | .New `enabled` alert meta option to disable a Pacemaker alert Pacemaker alerts and alert recipients now support an `enabled` meta option. Setting this option to `false` for an alert disables the alert. Setting this option to `true` for an alert and `false` for a particular recipient disables the alert for that recipient. The default value for this option is `true`. You can use this option to temporarily disable an alert for any reason, such as planned maintenance. |
||
| Steven J. Levine | 2023-08-17 13:37:27 UTC | Docs Contact | slevine |
Back to bug 2078611