Re-enabling Corosync/Cluster/HA after Proxmox VE Post Install disabled them?

[BlackrazorNZ]

Hi there,

How do I re-enable the Cluster parts of Proxmox after I previously had the Proxmox VE Post Install script disable them on initial install?

I only had 1 machine, however now I've added a 2nd and want to cluster them.

corosync, pve-ha-crm and pve-ha-lrm all show as disabled under node-System. I can start the latter 2 but not corosync, but I cannot switch their from disabled to enabled.

In the new machine, all 3 services are enabled.

Addtionally, in the original machine, no CIDR shows under the Create Cluster function:

The new 2nd machine, however, does have this:

I have tried re-running the original script as I note many others have a 'second use' different workflow or toggle option, however the option to reverse the original change is not presented if you re-run the script.

Any advice on how to manually enable these options?

Thank you!

[tteck]

systemctl enable --now pve-ha-lrm
systemctl enable --now pve-ha-crm
systemctl enable --now corosync

[tteck]

https://pve.proxmox.com/wiki/Cluster_Manager

[BlackrazorNZ]

No, it's not possible to enter it manually, you have to select an option from the drop down menu.

However I figured out what was causing it, so I thought I'd comment in case anyone else in in this circumstance. I have my Proxmox instance set to DHCP with a fixed IP address allocated by my DHCP server - I do this primarily for visibility purposes, and it works fine to date.

However, apparently unless you have an IP address physically set in /etc/network/interfaces, it will not show up in the Create Cluster CIDR dropdown. Here's my DHCP setup below - if I comment out the DHCP line and uncomment the static IP lines, the CIDR item shows up in the dropdown on reboot and then works fine.

I am going to do some more experimenting to identify if it's possible to manually set up the cluster via CLI while still having DHCP allocation - if so, I will update here.

[tteck]

Got it, so if you hadn't modified the /etc/network/interfaces file it would have worked after you re-enabled those services.

[tteck]

Why not set the static IP address and assign a DHCP reservation with the same IP?

[BlackrazorNZ]

Yes, that is what I will likely do. Thank you for your help :)