Bug 2167528
| Summary: | Fix stonith watchdog timeout | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Rich Megginson <rmeggins> | |
| Component: | rhel-system-roles | Assignee: | Tomas Jelinek <tojeline> | |
| Status: | CLOSED ERRATA | QA Contact: | michal novacek <mnovacek> | |
| Severity: | unspecified | Docs Contact: | Steven J. Levine <slevine> | |
| Priority: | unspecified | |||
| Version: | 9.2 | CC: | djez, efedin, mnovacek, spetrosi, tojeline | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | 9.2 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | role:ha_cluster | |||
| Fixed In Version: | rhel-system-roles-1.21.0-0.19.el9 | 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: | ||||
| : | 2167941 (view as bug list) | Environment: | ||
| Last Closed: | 2023-05-09 07:38:27 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: | ||||
| Bug Blocks: | 2167941 | |||
|
Description
Rich Megginson
2023-02-06 22:48:38 UTC
I have verified that `stonith-watchdog-timeout` is correctly set with `rhel-system-roles-1.21.0-0.19.el9` in the case that the cib.xml is modified when cluster is stopped. --- > [root@virt-566 ~]# cat test.yml - hosts: all vars: ha_cluster_hacluster_password: password ha_cluster_enable_repos: False ha_cluster_cluster_properties: - attrs: - name: stonith-watchdog-timeout value: 1201 tasks: - import_role: name: rhel-system-roles.ha_cluster > [root@virt-565 playbooks]# rpm -q rhel-system-roles pcs rhel-system-roles-1.21.0-0.19.el9.noarch pcs-0.11.4-4.el9.x86_64 > Check that with running cluster cib and signature are "synced". [root@virt-566 ~]# ls -l /var/lib/pacemaker/cib/cib.xml* -rw-------. 1 hacluster haclient 2503 Feb 17 12:26 /var/lib/pacemaker/cib/cib.xml -rw-------. 1 hacluster haclient 32 Feb 17 12:26 /var/lib/pacemaker/cib/cib.xml.sig > Observe the value of stonith-watchdog-timeout > [root@virt-566 ~]# pcs property Cluster Properties: cluster-infrastructure: corosync cluster-name: my-cluster dc-version: 2.1.5-5.el9-a3f44794f94 have-watchdog: true > stonith-watchdog-timeout: 1202 > Stop the cluster. > [root@virt-566 ~]# pcs cluster stop --all virt-566: Stopping Cluster (pacemaker)... virt-567: Stopping Cluster (pacemaker)... virt-567: Stopping Cluster (corosync)... virt-566: Stopping Cluster (corosync)... > Modify the cib by setting stonith-watchdog-timeout. > [root@virt-566 ~]# pcs -f /var/lib/pacemaker/cib/cib.xml property set stonith-watchdog-timeout=1203 > Observe signature not being updated. > [root@virt-566 ~]# ls -l /var/lib/pacemaker/cib/cib.xml* -rw-------. 1 hacluster haclient 2515 Feb 17 12:29 /var/lib/pacemaker/cib/cib.xml -rw-------. 1 hacluster haclient 32 Feb 17 12:26 /var/lib/pacemaker/cib/cib.xml.sig > run the playbook test.yml > Observe the value to be correctly set to playbook stonith-watchdog timeout value > [root@virt-566 ~]# pcs property Cluster Properties: cluster-infrastructure: corosync cluster-name: my-cluster dc-version: 2.1.5-5.el9-a3f44794f94 have-watchdog: true > stonith-watchdog-timeout: 1201 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:2246 |