Recent content by ishanjain

Interestingly, After all of this /etc/issue remains unchanged but it's a more aesthetic thing so I don't care about it.

Okay, It's fixed! and for future reference, The right way to fix this problem is like this. I'll take two nodes in my example. pvenas(10.0.99.9), pvepc(10.0.99.20 changed to 10.0.99.4) 1. Update /etc/hosts on pvepc by adding an entry like 10.0.99.4 pvepc.home.arpa pvepc 2. Run systemctl...

It looks like pve-cluster service is responsible for it. I tried the steps here and still no changes are made to /etc/pve/.members https://blog.dob.sk/2018/07/09/fix-invalid-node-ip-in-etc-pve-members/

/etc/pve/.members is readonly and I can't do chmod 600 on it even as a root user. Not sure how/what service is responsible for updating it

The /etc/issue entry on pvepc(machine with .20 address) shows 10.0.99.20 pvepc member in /etc/pve/.members on all machines points to 10.0.99.20

I don't want to put it back on .20. Please let me know if any one else knows whats going wrong here and how can i fix it, thanks! and thank you @waltar for teaching me how corosync updates are supposed to be done. Hopefully, Next time I will make less of a mess than I did now

I guess I can do that. I wanted a cleaner setup where all the proxmox nodes have addresses close to each other. .15 to .23 is now taken up by my wifi access points

This particular node (pvepc) is running vms with pci passthrough and I don't really want to migrate it to other nodes. Dejoining a node from the cluster is hell and I don't want to do that if I can avoid it some how.

I don't know if pve added(or tried adding) any entries to /etc/hosts. I had added this entry manually in all nodes. 10.0.99.4 pvepc.home.arpa pvepc After a reboot, I still have the same problem. Healthcheck passes but it still shows the old ip address and node is unreachable in the web ui

> Is the new IP in same network segment or outside the other nodes yet ? Same segment. I have rebooted it 3-4 times now but I'll do it again.

The problematic node is `pvepc`. It's actual IP address is 10.0.99.4 but in the web ui it still shows 10.0.99.20. In all corosync configs on all nodes, the ip address for pvepc is 10.0.99.4

ssh with new ip is working, ssh with old ip is not working.

Restarted pveproxy thinking that might solve the problem and it didn't.

I do not have any VMs or LXC containers in HA. I edited /etc/pve/corosync.conf, bumped config_version from 4 to 5, restarted corosync. The config was synced to all the other nodes correctly but in the web ui I still have the same problem. i.e. 1. The check next to the node in the list on the...

One of my node's IP that is part of the cluster has changed. I read a few threads here and they suggested changing the address in 1. /etc/hosts 2. /etc/network/interfaces(on the machine who's IP was changed) 3. /etc/corosync/corosync.conf and then reboot. I did all that and it still...