04/24/2023, 12:01 AM
I survived moving a node to a new network in the prior thread. Now things seem to be working, but Harvester remembers its old IP address for some reason. Is this as concerning as the red status pill and text implies?
Upgrading from v1.1.1 to v1.1.2 has failed because the node was moved to a new network prior to the upgrade. The cluster fails to start while looking for the old address
May 07 20:39:30 mira rke2[4955]: time="2023-05-07T20:39:30Z" level=info msg="Failed to test data store connection: this server is a not a member of the etcd cluster. Found [mira-0e38c95d=<>], expect: mira-0e38c95d=<>"
I finally noticed the Harvester install instructions state that changing the node IP is not possible. I wish I'd known that sooner.


05/08/2023, 12:51 AM
Is it possible to revert the IP change temporarily? etcd’s IP can’t be changed.


05/08/2023, 12:56 AM
That's good to know. I decided to create a new cluster.