Bug 1796824
Summary: | crm_node -l does not work inside a bundle that has pcmk_remote inside | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Michele Baldessari <michele> |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | bdobreli, cluster-maint, nwahl, phagara, pkomarov |
Target Milestone: | rc | ||
Target Release: | 8.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pacemaker-2.0.4-4.el8 | Doc Type: | Bug Fix |
Doc Text: |
Cause: Pacemaker Remote does not proxy local client connections to pacemakerd on the connection host.
Consequence: crm_node's -l and -p options do not work on a Pacemaker Remote node.
Fix: crm_node -l and -p now ask the controller (which is proxied) for information rather than pacemakerd.
Result: crm_node -l and -p work on a connected Pacemaker Remote node.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 04:00:53 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: |
Description
Michele Baldessari
2020-01-31 10:46:43 UTC
crm_node's -l and -p options contact the pacemakerd daemon to get the node list. Pacemaker Remote currently proxies connections to the controller, attribute manager, fencer, and CIB manager ... but not pacemakerd. I don't see any reason it shouldn't, so we should add that. Alternatively, we could make the controller handle those queries. Fixed upstream as of commit 8461509 before (2.0.3-5.el8_2.1) ======================== > [root@virt-078 ~]# pcs status > Cluster name: STSRHTS12473 > Cluster Summary: > * Stack: corosync > * Current DC: virt-079 (version 2.0.3-5.el8_2.1-4b1f869f0f) - partition with quorum > * Last updated: Wed Sep 23 12:34:42 2020 > * Last change: Wed Sep 23 12:34:38 2020 by root via cibadmin on virt-078 > * 4 nodes configured > * 5 resource instances configured > > Node List: > * Online: [ virt-078 virt-079 virt-080 ] > * RemoteOnline: [ virt-081 ] > > Full List of Resources: > * fence-virt-078 (stonith:fence_xvm): Started virt-079 > * fence-virt-079 (stonith:fence_xvm): Started virt-080 > * fence-virt-080 (stonith:fence_xvm): Started virt-080 > * fence-virt-081 (stonith:fence_xvm): Started virt-078 > * virt-081 (ocf::pacemaker:remote): Started virt-078 > > Daemon Status: > corosync: active/enabled > pacemaker: active/enabled > pcsd: active/enabled > [root@virt-078 ~]# ssh virt-081 crm_node -l > error: Could not connect to cluster (is it running?) > [root@virt-078 ~]# ssh virt-081 crm_node -p > error: Could not connect to cluster (is it running?) result: `crm_node -l` and `crm_node -p` commands can not be used from pacemaker remote nodes after (2.0.4-6.el8) =================== > [root@virt-187 ~]# pcs status > Cluster name: STSRHTS6022 > Cluster Summary: > * Stack: corosync > * Current DC: virt-189 (version 2.0.4-6.el8-2deceaa3ae) - partition with quorum > * Last updated: Wed Sep 23 12:34:47 2020 > * Last change: Wed Sep 23 12:32:15 2020 by root via cibadmin on virt-187 > * 4 nodes configured > * 5 resource instances configured > > Node List: > * Online: [ virt-187 virt-188 virt-189 ] > * RemoteOnline: [ virt-190 ] > > Full List of Resources: > * fence-virt-187 (stonith:fence_xvm): Started virt-188 > * fence-virt-188 (stonith:fence_xvm): Started virt-189 > * fence-virt-189 (stonith:fence_xvm): Started virt-189 > * fence-virt-190 (stonith:fence_xvm): Started virt-187 > * virt-190 (ocf::pacemaker:remote): Started virt-187 > > Daemon Status: > corosync: active/enabled > pacemaker: active/enabled > pcsd: active/enabled > [root@virt-187 ~]# ssh virt-190 crm_node -l > 1 virt-187 member > 2 virt-188 member > 3 virt-189 member > [root@virt-187 ~]# ssh virt-190 crm_node -p > virt-187 virt-188 virt-189 result: `crm_node -l` and `crm_node -p` commands can now be successfully used from pacemaker remote nodes 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/RHEA-2020:4804 |