Bug 2167941
Summary: | Fix stonith watchdog timeout | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Rich Megginson <rmeggins> |
Component: | rhel-system-roles | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | michal novacek <mnovacek> |
Severity: | unspecified | Docs Contact: | Steven J. Levine <slevine> |
Priority: | unspecified | ||
Version: | 8.8 | CC: | djez, efedin, mnovacek, rhel-cs-system-management-subsystem-qe, spetrosi, tojeline |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 8.8 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | role:ha_cluster | ||
Fixed In Version: | rhel-system-roles-1.21.0-0.19.el8 | Doc Type: | Bug Fix |
Doc Text: |
.Setting `stonith-watchdog-timeout` property with the `ha_cluster` System Role now works in a stopped cluster
Previously, when you set the `stonith-watchdog-timeout` property with the `ha_cluster` System Role in a stopped cluster, the property reverted to its previous value and the role failed. With this fix, configuring the `stonith-watchdog-timeout` property by using the `ha_cluster` System Role works properly.
|
Story Points: | --- |
Clone Of: | 2167528 | Environment: | |
Last Closed: | 2023-05-16 08:32:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2167528 | ||
Bug Blocks: |
Description
Rich Megginson
2023-02-07 18:22:51 UTC
I have verified that `stonith-watchdog-timeout` is correctly set with `rhel-system-roles-1.21.0-0.19.el8` in the case that the cib.xml is modified when cluster is stopped. The same method of verification was used as in bz2167528#c5 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:2804 |