Back to bug 2182482
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-03-28 19:42:03 UTC | Pool ID | sst_high_availability_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-03-28 19:42:59 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-153340 | |
| Klaus Wenninger | 2023-03-28 19:44:14 UTC | Assignee | kgaillot | kwenning |
| Status | NEW | POST | ||
| Shane Bradley | 2023-03-28 20:01:09 UTC | Link ID | Red Hat Knowledge Base (Solution) 6997664 | |
| Ken Gaillot | 2023-03-28 23:03:00 UTC | Dependent Products | Red Hat OpenStack | |
| Target Upstream Version | 2.1.6 | |||
| Target Release | --- | 9.3 | ||
| Chris Feist | 2023-04-17 16:00:52 UTC | CC | cfeist | |
| RHEL Program Management Team | 2023-04-17 16:02:38 UTC | Blocks | 2187424 | |
| RHEL Program Management Team | 2023-04-17 16:02:47 UTC | Blocks | 2187425 | |
| RHEL Program Management Team | 2023-04-17 16:02:56 UTC | Blocks | 2187426 | |
| RHEL Program Management Team | 2023-04-17 16:03:02 UTC | Keywords | ZStream | |
| Ken Gaillot | 2023-04-17 16:34:36 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | Cause: When fence_watchdog is used in a topology after another fencing device, the watchdog timeout would not be considered when calculating the timeout for the fencing operation. Consequence: If the first device timed out, the fencing operation could time out even though the watchdog would fence the node. Fix: The watchdog timeout is now included in the fencing operation timeout. Result: The fencing operation succeeds even if the first device times out. |
|||
| Dean Jansa | 2023-05-16 14:17:26 UTC | CC | jrehova | |
| Link ID | Red Hat Issue Tracker CLUSTERQE-6700 | |||
| Chris Lumens | 2023-05-23 20:44:46 UTC | Fixed In Version | pacemaker-2.1.6-1.el9 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-05-23 20:47:02 UTC | Status | MODIFIED | ON_QA |
| Martin Juricek | 2023-05-31 11:40:40 UTC | CC | mjuricek | |
| Status | ON_QA | VERIFIED | ||
| Steven J. Levine | 2023-06-28 20:22:44 UTC | CC | slevine | |
| Flags | needinfo?(kwenning) | |||
| Klaus Wenninger | 2023-06-29 03:02:43 UTC | Flags | needinfo?(kwenning) | |
| Steven J. Levine | 2023-07-07 18:00:46 UTC | Doc Text | Cause: When fence_watchdog is used in a topology after another fencing device, the watchdog timeout would not be considered when calculating the timeout for the fencing operation. Consequence: If the first device timed out, the fencing operation could time out even though the watchdog would fence the node. Fix: The watchdog timeout is now included in the fencing operation timeout. Result: The fencing operation succeeds even if the first device times out. | .A fence watchdog configured as a second fencing device now fences a node when the first device times out Previously, when a watchdog fencing device was configured as the second device in a fencing topology, the watchdog timeout would not be considered when calculating the timeout for the fencing operation. As a result, if the first device timed out the fencing operation would time out even though the watchdog would fence the node. With this fix, the watchdog timeout is included in the fencing operation timeout and the fencing operation succeeds if the first device times out. |
| Steven J. Levine | 2023-07-27 14:57:49 UTC | Docs Contact | slevine | |
| Red Hat Bugzilla | 2023-08-10 15:39:56 UTC | CC | cluster-qe | |
| QA Contact | cluster-qe | cluster-qe |
Back to bug 2182482