Bug 1126998
Summary: | pacemaker uses 'uname -n' if no nodename defined, which is confusing | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | John Ruemker <jruemker> |
Component: | pcs | Assignee: | Chris Feist <cfeist> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | cfeist, cluster-maint, dvossel, jkortus, rsteiger, tojeline, wagh1.ravi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pcs-0.9.134-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-05 09:20:26 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
John Ruemker
2014-08-05 20:11:07 UTC
Unless I misunderstand something, this is expected and by design. IP addresses are not valid node names and are not at all interchangeable with shortname or shortname.domain.name Even shortname, othershortname and shortname.domain.name are not interchangeable just because they map to the same IP in DNS. I would agree that the names under 'PCSD Status' should match the 'Online' section though. Do you have an opinion there Chris? I talked with Andrew and I think the solution to this is in the PCSD Status section I'll include the output from (uname -n) on all the nodes as well as the node name in the corosync section (with the ip address in parenthesis after). I'll also include a warning message if the corosync & pacemaker nodes are not identical. why are IPs not valid node names? I'm asking because we've run into similar issues when using ad-hoc rings that are not in DNS. The guess pacemaker makes to fill in node name has caused more trouble for me then it brought benefits ;). Patch upstream here: https://github.com/feist/pcs/commit/b7e0144fe84e953fab198bef376a952fbfcdcad5 Before Fix: [root@rh70-node1:~]# rpm -q pcs pcs-0.9.115-32.el7.x86_64 [root@rh70-node1:~]# pcs cluster auth 192.168.122.101 192.168.122.102 Username: hacluster Password: 192.168.122.101: Authorized 192.168.122.102: Authorized [root@rh70-node1:~]# pcs cluster setup 192.168.122.101 192.168.122.102 --name mycluster Shutting down pacemaker/corosync services... Redirecting to /bin/systemctl stop pacemaker.service Redirecting to /bin/systemctl stop corosync.service Killing any remaining services... Removing all cluster configuration files... 192.168.122.101: Succeeded 192.168.122.102: Succeeded [root@rh70-node1:~]# pcs cluster start --all 192.168.122.101: Starting Cluster... 192.168.122.102: Starting Cluster... [root@rh70-node1:~]# pcs status Cluster name: mycluster WARNING: no stonith devices and stonith-enabled is not false Last updated: Tue Oct 21 14:25:11 2014 Last change: Tue Oct 21 14:21:36 2014 Stack: corosync Current DC: rh70-node1 (1) - partition with quorum Version: 1.1.12-a14efad 2 Nodes configured 0 Resources configured Online: [ rh70-node1 rh70-node2 ] Full list of resources: PCSD Status: 192.168.122.101: Online 192.168.122.102: Online Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled After Fix: [root@rh70-node1:~]# rpm -q pcs pcs-0.9.134-1.el7.x86_64 [root@rh70-node1:~]# pcs cluster auth 192.168.122.101 192.168.122.102 Username: hacluster Password: 192.168.122.101: Authorized 192.168.122.102: Authorized [root@rh70-node1:~]# pcs cluster setup 192.168.122.101 192.168.122.102 --name mycluster Shutting down pacemaker/corosync services... Redirecting to /bin/systemctl stop pacemaker.service Redirecting to /bin/systemctl stop corosync.service Killing any remaining services... Removing all cluster configuration files... 192.168.122.101: Succeeded 192.168.122.102: Succeeded [root@rh70-node1:~]# pcs cluster start --all 192.168.122.101: Starting Cluster... 192.168.122.102: Starting Cluster... [root@rh70-node1:~]# pcs status Cluster name: mycluster WARNING: no stonith devices and stonith-enabled is not false WARNING: corosync and pacemaker node names do not match (IPs used in setup?) Last updated: Tue Oct 21 16:09:36 2014 Last change: Tue Oct 21 15:52:26 2014 Stack: corosync Current DC: rh70-node1 (1) - partition with quorum Version: 1.1.12-a14efad 2 Nodes configured 0 Resources configured Online: [ rh70-node1 rh70-node2 ] Full list of resources: PCSD Status: rh70-node1 (192.168.122.101): Online rh70-node2 (192.168.122.102): Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled note the "WARNING: corosync and pacemaker node names do not match (IPs used in setup?)" line Created pacemaker follow up as https://bugzilla.redhat.com/show_bug.cgi?id=1183103 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, 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://rhn.redhat.com/errata/RHBA-2015-0415.html I just changed ring0_addr from ip to hostname. Solved issue |