[ClusterLabs] pcs add node command is success but node is not configured to existing cluster

[Strahil Nikolov]

Firewall issue ?
Did you check on corosync level if all nodes reach each other ?

Best Regards,
Strahil Nikolov






В сряда, 28 юли 2021 г., 16:32:51 ч. Гринуич+3, S Sathish S via Users <users at clusterlabs.org> написа: 





  


Hi Team,

 

we are trying to add node03 to existing cluster after adding we could see only 2 nodes are configured and validated corosync log also "Waiting for all cluster members. Current votes: 2 expected_votes: 3" but in node3 pcs cluster status output it show 3 nodes are configured and no resource are listing but in node02 we have 40 resource configured which is not reflecting on node03.

 

This issue occur only on few problematic hardware not on all hardware , we don’t know why this is joining into cluster.

 

[root at node02 ~]# pcs cluster status

Cluster Status:

Stack: corosync

Current DC: node01 (version 2.0.2-744a30d655) - partition WITHOUT quorum

Last updated: Wed Jul 28 14:58:13 2021

Last change: Wed Jul 28 14:41:41 2021 by root via cibadmin on node01

2 nodes configured

40 resources configured

 

PCSD Status:

  node02: Online

  node01: Online

  node03: Online

[root at node02 ~]#

 

Corosync log on node added execution :

Jul 28 11:15:05 [17598] node01 corosync notice  [TOTEM ] A new membership (10.216.x.x:42660) was formed. Members

Jul 28 11:15:05 [17598] node01 corosync notice  [QUORUM] Members[2]: 1 2

Jul 28 11:15:05 [17598] node01 corosync notice  [MAIN  ] Completed service synchronization, ready to provide service.

Jul 28 11:15:05 [17598] node01 corosync notice  [CFG   ] Config reload requested by node 1

Jul 28 11:15:05 [17598] node01 corosync notice  [TOTEM ] adding new UDPU member {10.216.x.x}

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:07 [17599] node01 corosync notice  [TOTEM ] A new membership (10.216.x.x:42664) was formed. Members

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:07 [17599] node01 corosync notice  [QUORUM] This node is within the non-primary component and will NOT provide any services.

Jul 28 11:15:07 [17599] node01 corosync notice  [QUORUM] Members[2]: 1 2

Jul 28 11:15:07 [17599] node01 corosync notice  [MAIN  ] Completed service synchronization, ready to provide service.

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:07 [17599] node01 corosync notice  [VOTEQ ] Waiting for all cluster members. Current votes: 2 expected_votes: 3

Jul 28 11:15:11 [17599] node01 corosync notice  [TOTEM ] A new membership (10.216.x.x:42668) was formed. Members

 

 

[root at node03 ~]# pcs cluster status

Cluster Status:

Stack: corosync

Current DC: node03 (version 2.0.2-744a30d655) - partition WITHOUT quorum

Last updated: Wed Jul 28 15:04:31 2021

Last change: Wed Jul 28 15:04:00 2021 by root via cibadmin on node03

3 nodes configured

0 resources configured

 

PCSD Status:

  node03: Online

  node01: Online

  node02: Online

[root at node03 ~]#

 

Thanks and Regards,

S Sathish S



_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/