This message was deleted.
# harvestera
adamant-kite-43734
12/14/2023, 7:03 PMThis message was deleted.
b
bright-address-34562
12/14/2023, 9:45 PMis it as simple as just replacing the two ip addresses in /oem/* and restarting the host?
bright-address-34562
12/14/2023, 11:03 PMseems not, I get a certificate error:
Dec 14 23:02:28 harvester1 rke2[2489]: time="2023-12-14T23:02:28Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="x509: certificate is valid for 10.0.100.2, 10.0.100.30, 10.53.0.1, 127.0.0.1, ::1, not 10.0.3.2"bright-address-34562
12/14/2023, 11:04 PMand also
Dec 14 23:03:27 harvester1 rke2[2489]: time="2023-12-14T23:03:27Z" level=info msg="Failed to test data store connection: this server is a not a member of the etcd cluster. Found [harvester1-a2b4cffc=<https://10.0.100.2:2380>], expect: harvester1-a2b4cffc=<https://10.0.3.2:23>>s
stale-cpu-21467
12/16/2023, 2:22 AMit will be tough.
I believe we need to locate and update all config under /etc, and the cert must be regenerated with the new IP in altername.
https://github.com/kubernetes/kubeadm/issues/338#issuecomment-418879755
this is how they do it with kubeadm
b
bright-address-34562
12/16/2023, 2:24 AMthanks for the info, I thought as much and decided to just scrap the server and reinstall. gave me an opportunity to test out the vm backup/restore feature 😊
🙌 1
bright-address-34562
12/16/2023, 3:24 AMI removed a cdrom image from one restored vm and it boots and runs fine, but it is stuck as "restoring" in the vm list.. happen to know how to fix that?
3 Views