Back to bug 2187426
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-04-17 16:02:56 UTC | Pool ID | sst_high_availability_rhel_9 | |
| RHEL Program Management Team | 2023-04-17 16:02:59 UTC | Link ID | Red Hat Knowledge Base (Solution) 6997664 | |
| Red Hat One Jira (issues.redhat.com) | 2023-04-17 16:03:30 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-154952 | |
| Ken Gaillot | 2023-04-17 16:35:21 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Target Upstream Version | 2.1.6 | |||
| Status | NEW | POST | ||
| Type | --- | Bug | ||
| 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. |
|||
| Martin Juricek | 2023-06-01 08:46:45 UTC | CC | mjuricek | |
| Klaus Wenninger | 2023-06-13 12:40:37 UTC | Fixed In Version | pacemaker-2.1.2-4.el9_0.4 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-06-13 12:41:52 UTC | Status | MODIFIED | ON_QA |
| Martin Juricek | 2023-06-14 08:42:26 UTC | Status | ON_QA | VERIFIED |
| Red Hat Bugzilla | 2023-08-10 15:40:26 UTC | CC | cluster-qe | |
| QA Contact | cluster-qe | cluster-qe |
Back to bug 2187426