Bug 1203802
| Summary: | Cluster setup overwrites cluster.conf on RHEL6 without warning | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Radek Steiger <rsteiger> | ||||
| Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.7 | CC: | cluster-maint, tojeline | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pcs-0.9.145-1.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause:
User creates a cluster using nodes which are part of another cluster.
Consequence:
Existing cluster configuration on the nodes gets overwritten by the newly created cluster configuration.
Fix:
Check whether nodes are part of a cluster, exit with an error message if they are.
Result:
User does not accidentally destroy an existing cluster by running the 'pcs cluster setup' command.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-05-10 19:27:41 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: | |||||||
| Attachments: |
|
||||||
|
Description
Radek Steiger
2015-03-19 17:14:24 UTC
Created attachment 1078403 [details] proposed fix Before fix: [root@rh67-node1:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node2:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node3:~]# ls /etc/cluster/cluster.conf ls: cannot access /etc/cluster/cluster.conf: No such file or directory [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 Warning: Unable to set pcsd configs on rh67-node1 Warning: Unable to set pcsd configs on rh67-node2 rh67-node1: Updated cluster.conf... rh67-node2: Updated cluster.conf... rh67-node3: Updated cluster.conf... Synchronizing pcsd certificates on nodes rh67-node1, rh67-node2, rh67-node3... rh67-node2: Success rh67-node3: Success rh67-node1: Success Restaring pcsd on the nodes in order to reload the certificates... rh67-node2: Success rh67-node3: Success rh67-node1: Success > No warning saying nodes are already part of a cluster is displayed, existing cluster config files get overwritten. After fix: [root@rh67-node1:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node2:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node3:~]# ls /etc/cluster/cluster.conf ls: cannot access /etc/cluster/cluster.conf: No such file or directory [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 Error: rh67-node1: node is already in a cluster Error: rh67-node2: node is already in a cluster Error: nodes availability check failed, use --force to override. WARNING: This will destroy existing cluster on the nodes. [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 --force Destroying cluster on nodes: rh67-node1, rh67-node2, rh67-node3... rh67-node2: Stopping Cluster (pacemaker)... rh67-node3: Stopping Cluster (pacemaker)... rh67-node1: Stopping Cluster (pacemaker)... rh67-node3: Successfully destroyed cluster rh67-node1: Successfully destroyed cluster rh67-node2: Successfully destroyed cluster Sending cluster config files to the nodes... rh67-node1: Updated cluster.conf... rh67-node2: Updated cluster.conf... rh67-node3: Updated cluster.conf... Synchronizing pcsd certificates on nodes rh67-node1, rh67-node2, rh67-node3... rh67-node2: Success rh67-node3: Success rh67-node1: Success Restaring pcsd on the nodes in order to reload the certificates... rh67-node2: Success rh67-node3: Success rh67-node1: Success > Pcs prints a warning saying nodes are already part of a cluster and does not proceed. User is able to force the operation. In that case the existing cluster is properly destroyed on the nodes prior to set up a new one. Before Fix: [root@rh67-node1 ~]# rpm -q pcs pcs-0.9.139-9.el6_7.1.x86_64 [root@rh67-node2 ~]# rpm -q pcs pcs-0.9.139-9.el6_7.1.x86_64 [root@rh67-node3 ~]# rpm -q pcs pcs-0.9.139-9.el6_7.1.x86_64 [root@rh67-node1:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node2:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node3:~]# ls /etc/cluster/cluster.conf ls: cannot access /etc/cluster/cluster.conf: No such file or directory [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 rh67-node1: Updated cluster.conf... rh67-node2: Updated cluster.conf... rh67-node3: Updated cluster.conf... > No warning saying nodes are already part of a cluster is displayed, existing cluster config files get overwritten. After Fix: [root@rh67-node1:~]# rpm -q pcs pcs-0.9.145-1.el6.x86_64 [root@rh67-node2:~]# rpm -q pcs pcs-0.9.145-1.el6.x86_64 [root@rh67-node3:~]# rpm -q pcs pcs-0.9.145-1.el6.x86_64 [root@rh67-node1:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node2:~]# ls /etc/cluster/cluster.conf /etc/cluster/cluster.conf [root@rh67-node3:~]# ls /etc/cluster/cluster.conf ls: cannot access /etc/cluster/cluster.conf: No such file or directory [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 Error: rh67-node1: node is already in a cluster Error: rh67-node2: node is already in a cluster Error: nodes availability check failed, use --force to override. WARNING: This will destroy existing cluster on the nodes. [root@rh67-node3:~]# echo $? 1 [root@rh67-node3:~]# pcs cluster setup --name cluster67 rh67-node1 rh67-node2 rh67-node3 --force Destroying cluster on nodes: rh67-node1, rh67-node2, rh67-node3... rh67-node3: Stopping Cluster (pacemaker)... rh67-node1: Stopping Cluster (pacemaker)... rh67-node2: Stopping Cluster (pacemaker)... rh67-node3: Successfully destroyed cluster rh67-node1: Successfully destroyed cluster rh67-node2: Successfully destroyed cluster Sending cluster config files to the nodes... rh67-node1: Updated cluster.conf... rh67-node2: Updated cluster.conf... rh67-node3: Updated cluster.conf... Synchronizing pcsd certificates on nodes rh67-node1, rh67-node2, rh67-node3... rh67-node2: Success rh67-node3: Success rh67-node1: Success Restaring pcsd on the nodes in order to reload the certificates... rh67-node2: Success rh67-node3: Success rh67-node1: Success [root@rh67-node3:~]# echo $? 0 > Pcs prints a warning saying nodes are already part of a cluster and does not proceed. User is able to force the operation. In that case the existing cluster is properly destroyed on the nodes before a new cluster is set up. 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-2016-0739.html |