Bug 2163450
Summary: | Removing remote node results in a fence action | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Michal Mazourek <mmazoure> | |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> | |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 9.2 | CC: | cluster-maint, jrehova, msmazova | |
Target Milestone: | rc | Keywords: | Regression, Triaged | |
Target Release: | 9.2 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | pacemaker-2.1.5-5.el9 | Doc Type: | No Doc Update | |
Doc Text: |
This was not in a released build
|
Story Points: | --- | |
Clone Of: | ||||
: | 2163567 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-09 07:18:17 UTC | Type: | Bug | |
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: | 2163567 |
Description
Michal Mazourek
2023-01-23 14:30:06 UTC
The root cause is different from bz2039399 and was introduced by upstream commit d61494347, which was based on an incorrect analysis of bz1804259 and thus simply needs to be reverted. * 4 nodes cluster Version of pacemaker: > [root@virt-313 ~]# rpm -qa pacemaker > pacemaker-2.1.5-5.el9.x86_64 Status of cluster: > [root@virt-313 ~]# pcs status > Cluster name: STSRHTS23870 > Status of pacemakerd: 'Pacemaker is running' (last updated 2023-01-31 14:22:55 +01:00) > Cluster Summary: > * Stack: corosync > * Current DC: virt-315 (version 2.1.5-5.el9-a3f44794f94) - partition with quorum > * Last updated: Tue Jan 31 14:22:56 2023 > * Last change: Tue Jan 31 14:00:48 2023 by root via cibadmin on virt-313 > * 4 nodes configured > * 4 resource instances configured > > Node List: > * Online: [ virt-313 virt-314 virt-315 virt-316 ] > > Full List of Resources: > * fence-virt-313 (stonith:fence_xvm): Started virt-313 > * fence-virt-314 (stonith:fence_xvm): Started virt-314 > * fence-virt-315 (stonith:fence_xvm): Started virt-315 > * fence-virt-316 (stonith:fence_xvm): Started virt-316 > > Daemon Status: > corosync: active/disabled > pacemaker: active/disabled > pcsd: active/enabled Remove node virt-316: > [root@virt-313 ~]# pcs cluster node remove virt-316 > Destroying cluster on hosts: 'virt-316'... > virt-316: Successfully destroyed cluster > Sending updated corosync.conf to nodes... > virt-313: Succeeded > virt-315: Succeeded > virt-314: Succeeded > virt-315: Corosync configuration reloaded Install package pacemaker-remote on node, that is chosen to be remote: > [root@virt-316 ~]# yum install pacemaker-remote Create remote node: > [root@virt-313 ~]# pcs cluster node add-remote virt-316 > No addresses specified for host 'virt-316', using 'virt-316' > Sending 'pacemaker authkey' to 'virt-316' > virt-316: successful distribution of the file 'pacemaker authkey' > Requesting 'pacemaker_remote enable', 'pacemaker_remote start' on 'virt-316' > virt-316: successful run of 'pacemaker_remote enable' > virt-316: successful run of 'pacemaker_remote start' Status of cluster: > [root@virt-313 ~]# pcs status | grep "Node List" -A 2 > Node List: > * Online: [ virt-313 virt-314 virt-315 ] > * RemoteOnline: [ virt-316 ] Remove remote node: > [root@virt-313 ~]# pcs cluster node remove-remote virt-316 > Requesting 'pacemaker_remote disable', 'pacemaker_remote stop' on 'virt-316' > virt-316: successful run of 'pacemaker_remote disable' > virt-316: successful run of 'pacemaker_remote stop' > Requesting remove 'pacemaker authkey' from 'virt-316' > virt-316: successful removal of the file 'pacemaker authkey' > Deleting Resource - virt-316 > [root@virt-313 ~]# echo $? > 0 > [root@virt-313 ~]# pcs stonith history > 0 events found Result: No fence action occured. 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 (pacemaker 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/RHBA-2023:2150 |