Back to bug 2187423
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-04-17 16:02:12 UTC | Pool ID | sst_high_availability_rhel_8 | |
| RHEL Program Management Team | 2023-04-17 16:02:14 UTC | Link ID | Red Hat Knowledge Base (Solution) 6997664 | |
| Red Hat One Jira (issues.redhat.com) | 2023-04-17 16:03:20 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-154949 | |
| Ken Gaillot | 2023-04-17 16:33:41 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Type | --- | Bug | ||
| Status | NEW | POST | ||
| 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. | |||
| Target Upstream Version | 2.1.6 | |||
| Martin Juricek | 2023-05-16 07:59:57 UTC | CC | mjuricek | |
| Chris Lumens | 2023-05-17 14:51:10 UTC | Fixed In Version | pacemaker-2.0.5-9.el8_4.6 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-05-17 17:30:54 UTC | Status | MODIFIED | ON_QA |
| Martin Juricek | 2023-05-23 08:05:16 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2023-06-13 08:15:39 UTC | Status | VERIFIED | RELEASE_PENDING |
| Flavio Piccioni | 2023-07-04 09:02:48 UTC | CC | fpiccion | |
| errata-xmlrpc | 2023-07-25 07:52:59 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-07-25 07:52:59 UTC | |||
| errata-xmlrpc | 2023-07-25 07:53:01 UTC | Link ID | Red Hat Product Errata RHBA-2023:4253 |
Back to bug 2187423