github avandeputte/haproxy-manager v2.4.1
2.4.1: asking for betas is one setting for the whole cluster

one hour ago

2.4.1: asking for betas is one setting for the whole cluster

One fix, for clusters. Upgrading a cluster: update every node (see Updates).

Also offer beta versions, on the Updates page, was saved on the node it was ticked on. In a cluster the other nodes never heard of it, so the Updates page offered different versions depending on which node it was opened on, and the tick seemed to come and go when the virtual IP moved. A node updated on its own could end up on a beta while the others stayed on the release. Reported in #39.

The tick is now part of the shared configuration:

  • Ticked on any node, every node offers the same versions. On a passive node the choice is made on the node holding the virtual IP, and the page says which node that was.
  • The other nodes have it within a minute, and check for the beta at once.
  • A tick you already made is kept. Each node hands its own tick to the cluster when it starts on 2.4.1; a passive node waits for the node holding the virtual IP to be updated too.
  • Nothing is left waiting for an Apply after ticking or unticking.
  • A single node behaves as before, and so does a Proxmox container's update.

Tested on a three-node cluster with a virtual IP, started on 2.4.0 and updated node by node: a tick made on one passive node reached all three; ticking and unticking from passive and active nodes; a failover; a node that was down while the choice changed. Not tried: a systemd host, and the Proxmox update script itself.

Don't miss a new haproxy-manager release

NewReleases is sending notifications on new releases.