This message was deleted.
# harvester
a
This message was deleted.
b
I figured one thing out; I can download the ssh key from rancher and use that to connect to the vm, where I was able to figure out one misconfiguration issue I had with DNS on the VLAN, at least.. let's see how much further I can get this time
1
b
Were you able to make progress on this? Did the guest VM have any more clues?
b
yeah, that one particular issue was just the dns, so got past that, but I'm having some more severe issues following a crash atm
that error has fixed itself by now, but there are 2 nodes not joining the cluster.. I logged into one of them, and syslog is spamming these messages over and over..
Copy code
Dec 14 01:42:06 infra-pool1-12e24e65-b5g5p rke2[2312]: {"level":"warn","ts":"2023-12-14T01:42:06.955856Z","logger":"etcd-client","caller":"v3@v3.5.9-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"<etcd-endpoints://0xc0006a48c0/10.0.30.21:2379>","attempt":0,"error":"rpc error: code = Unavailable desc = etcdserver: unhealthy cluster"}
Dec 14 01:42:06 infra-pool1-12e24e65-b5g5p rke2[2312]: time="2023-12-14T01:42:06Z" level=info msg="Waiting for other members to finish joining etcd cluster: etcdserver: unhealthy cluster"
I gave up and deleted the cluster and recreated it, will see if it comes up by tomorrow 😛
hmm, no, the new cluster has been like this for 6 hours now;