Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

ISO 3.2.1 Failed to create cluster when adding 3rd node


at
4 Posts
August 13, 2023, 7:40 am

I tried to create the cluster many times using the new ISO 3.2.1, but I always get this error:

Error building cluster, please check detail below.

Error List

Error building Consul cluster.

I tried the same installation using ISO 3.2.0 and it works fine, and all nodes are joined correctly.

Last edited on August 13, 2023, 7:40 am by at · #1

admin
2,930 Posts
August 13, 2023, 10:01 am

i just downloaded iso and it works fine.

consul is the first clustered service we build in the deployment, it is most likely there is an issue with your backend network setup. maybe swicth bond settings or mtu frames. try deploy without bonding and mtu frames first to debug such issues, also check your ips/subnets do not overlap...etc

Last edited on August 13, 2023, 10:02 am by admin · #2

at
4 Posts
August 13, 2023, 8:49 pm

Thanks for your fast response,

Yes, I am using bonding and Jumbo Frames.
I was able to reinstall the cluster by disabling Jumbo Frames, and Bonding. Then I edited the cluster_info.json

nano /opt/petasan/config/cluster_info.json

{
"backend_1_base_ip": "10.1.0.0",
"backend_1_eth_name": "bond0",
"backend_1_mask": "255.255.255.0",
"backend_1_vlan_id": "",
"backend_2_base_ip": "",
"backend_2_eth_name": "",
"backend_2_mask": "",
"backend_2_vlan_id": "",
"bonds": [
{
"interfaces": "eth2,eth3",
"is_jumbo_frames": true,
"mode": "802.3ad",
"name": "bond0",
"primary_interface": ""
}
],
"default_pool": "",
"default_pool_pgs": "0",
"default_pool_replicas": "",
"eth_count": 4,
"jf_mtu_size": "9000",
"jumbo_frames": [
"eth1",
"eth2",
"eth3"
],
"management_eth_name": "eth0",

rebooted the cluster and everything seems to be working fine, OSDs created successfully

 

Last edited on August 13, 2023, 8:50 pm by at · #3

admin
2,930 Posts
August 13, 2023, 9:33 pm

thanks for the feedback, maybe the bonds/mtu were not entered correctly in the ui ? there has been no changes with 3.2.0

#4

at
4 Posts
August 13, 2023, 9:50 pm

I tested the same configuration on 3.2.0 and failed to continue using the UI!!!, I installed the system a 3 weeks ago using UI without any problems. I have no clue what is the root cause for the problem.
I can't correlate this problem to network level as the manual configuration worked directly.

Last edited on August 13, 2023, 10:09 pm by at · #5

admin
2,930 Posts
August 13, 2023, 10:34 pm

You mean it worked 3 weeks ago using 3.2.0 but did not work recently ?

Is it possible you install a dummy node (such as vm on your desktop)  and deploy only this node to create a dummy cluster with similar configuration of bond/mtu. you do not have to install other nodes, then grab the cluster_info.json file and see how it compares with the current config file. it could help know which step was not set up correctly.

#6

at
4 Posts
August 14, 2023, 1:07 am

I can't grab the old configuration fie, as the system is built on real production servers. First phase was evaluation of ver 3.2

 

#7

admin
2,930 Posts
August 14, 2023, 2:44 am

i just want the config file of the test vm, so to compare with file of current working cluster posted above.

 

#8