NoVNC Not Connecting After Clustering (When part of cluster is off)

[bobiii84]

Hopefully I'm posting this in the correct place, I rarely have occasion to post on here. I recently setup a cluster with two boxes, mostly because I was curious how it worked. I turned off one part of the cluster because I wasn't using it, then noticed I could not NoVNC into the VMs I had on the part of the cluster that is still online.

I verified this by turning on the empty box that's part of the cluster, and voila, suddenly my NoVNC worked for the rest of the cluster VMs.

The cluster is setup on my main box, the empty box joined it, so I'm confused why I'm having this issue. I could have imagined this being an issue if I made the primary system on the cluster the empty box and turned it off, but not this way around. Is this something anyone is familiar with? I don't want to have to turn on the entire cluster each time to make it work, nor do I really want to de-cluster them (But I will, if needed). TYIA!

 

[Neobin]

• In a PVE-cluster, there is no master- or main-node. All are equal.
• If the cluster is not quorate [1] and in case no HA [2] is set up, it will go in read-only mode.
• If the cluster is not quorate [1] and in case HA [2] is set up, it will even go further and starts fencing [3] and reboot the node(s).
• With only two nodes, it is highly recommended to set up an independent QDevice [4] in any case.

So, a QDevice should help in your situation also as a "workaround"; but generally in a PVE-cluster it is assumed, that all nodes of it are ever online and reachable.

[1] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_quorum
[2] https://pve.proxmox.com/pve-docs/chapter-ha-manager.html
[3] https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#ha_manager_fencing
[4] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_corosync_external_vote_support

 

[bobiii84]

• In a PVE-cluster, there is no master- or main-node. All are equal.
• If the cluster is not quorate [1] and in case no HA [2] is set up, it will go in read-only mode.
• If the cluster is not quorate [1] and in case HA [2] is set up, it will even go further and starts fencing [3] and reboot the node(s).
• With only two nodes, it is highly recommended to set up an independent QDevice [4] in any case.

So, a QDevice should help in your situation also as a "workaround"; but generally in a PVE-cluster it is assumed, that all nodes of it are ever online and reachable.

[1] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_quorum
[2] https://pve.proxmox.com/pve-docs/chapter-ha-manager.html
[3] https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#ha_manager_fencing
[4] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_corosync_external_vote_support

I ended up having some weird issues and decided to remove the cluster. I don't really need it, was just curious. Really appreciate your quick response!