Forums

Home / Forums

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

Node listed twice


jpowell@mobilcomm.com
5 Posts
August 29, 2025, 2:57 am

I had a failure of the OS HDD on one of my management nodes.  Simple enough to pop a new HDD in and re-install as replace node.  My problem is that node is listed twice in the node list.  Where might I find this "setting" and clear out the duplicate?

 

 

#1

admin
3,054 Posts
August 29, 2025, 6:51 pm

Simple enough to pop a new HDD in and re-install as replace node

you replaced he HDD, not the node, correct ?

#2

jpowell@mobilcomm.com
5 Posts
August 29, 2025, 6:52 pm

Correct. Everything is up and running fine.  The only issue is I see the node in the node list twice.

#3

admin
3,054 Posts
August 31, 2025, 3:05 pm

Can you post output of

consul kv get -recurse PetaSAN/Nodes

 

Have you done any previous node replacements ? changed hostnames ?

#4

jpowell@mobilcomm.com
5 Posts
September 8, 2025, 1:13 pm

Yes, I had a little struggle in the beginning getting things running.   I do see #2 listed twice.

 

PetaSAN/Nodes/MC-PetaSAN-01:{
"backend_1_ip": "172.16.41.1",
"backend_2_ip": "",
"is_backup": true,
"is_cifs": false,
"is_iscsi": true,
"is_management": true,
"is_nfs": false,
"is_s3": false,
"is_storage": true,
"management_ip": "192.168.43.44",
"name": "MC-PetaSAN-01",
"petasan_version": "4.0.0",
"running_kernel": "5.14.21-08-petasan"
}
PetaSAN/Nodes/MC-PetaSAN-02:{
"backend_1_ip": "172.16.41.2",
"backend_2_ip": "",
"is_backup": true,
"is_cifs": false,
"is_iscsi": true,
"is_management": true,
"is_nfs": false,
"is_s3": false,
"is_storage": true,
"management_ip": "192.168.43.45",
"name": "MC-PetaSAN-02",
"petasan_version": "4.0.0",
"running_kernel": "5.14.21-08-petasan"
}
PetaSAN/Nodes/MC-PetaSAN-03:{
"backend_1_ip": "172.16.41.3",
"backend_2_ip": "",
"is_backup": true,
"is_cifs": false,
"is_iscsi": true,
"is_management": true,
"is_nfs": false,
"is_s3": false,
"is_storage": true,
"management_ip": "192.168.43.46",
"name": "MC-PetaSAN-03",
"petasan_version": "4.0.0",
"running_kernel": "5.14.21-08-petasan"
}
PetaSAN/Nodes/MC-PetaSAN-04:{
"backend_1_ip": "172.16.41.4",
"backend_2_ip": "",
"is_backup": true,
"is_cifs": false,
"is_iscsi": true,
"is_management": false,
"is_nfs": false,
"is_s3": false,
"is_storage": true,
"management_ip": "192.168.43.47",
"name": "MC-PetaSAN-04",
"petasan_version": "4.0.0",
"running_kernel": "5.14.21-08-petasan"
}
PetaSAN/Nodes/PetaSAN-02:{
"backend_1_ip": "172.16.41.2",
"backend_2_ip": "",
"is_backup": true,
"is_cifs": false,
"is_iscsi": true,
"is_management": true,
"is_nfs": false,
"is_s3": false,
"is_storage": true,
"management_ip": "192.168.43.45",
"name": "MC-PetaSAN-02",
"petasan_version": "4.0.0",
"running_kernel": "5.14.21-08-petasan"

#5

jpowell@mobilcomm.com
5 Posts
September 8, 2025, 1:25 pm

Ah - I see the issue.  At one point While rebuilding #2 ( I ended up having hardware issues that I mistakenly thought was me not following the install process correctly)  I named the machine wrong.  (MC-petaSAN-02 vs PetaSAN-02)

 

Is there an easy way to delete this?  I do not know that it is affecting function, however it is confusing and messy at best.

#6

jpowell@mobilcomm.com
5 Posts
September 8, 2025, 7:18 pm

That was actually easy.

 

" consul kv delete PetaSAN/Nodes/PetaSAN-02"

#7