This message was deleted.
# rke2a
adamant-kite-43734
05/09/2023, 4:28 PMThis message was deleted.
d
dazzling-insurance-3854
05/09/2023, 6:05 PMI was able to get the cluster working again by changing a node hostname and then run the uninstall script, then make it join the cluster again, also deleted the rancher folders in
/etc/var/libdazzling-insurance-3854
05/09/2023, 6:05 PMHowever unique hostnames and that workaround doesn't seem to scale
dazzling-insurance-3854
05/09/2023, 6:06 PMwell, maybe scale is not the right word, but for my use-case hostname re-use would be common, as node goes away, node goes back in sort of thing
dazzling-insurance-3854
05/09/2023, 6:37 PMfor the time being, I will append a uuid to the hostnames and see if that makes this pain go away
t
tall-raincoat-70627
05/10/2023, 5:13 AMd
dazzling-insurance-3854
05/10/2023, 2:16 PMYes, it looks like the same issue, I was able to "overcome" the issue by adding a few lines to the cloudinit script to generate a somewhat unique hostname, but it is just a hack to make it work
20 Views