We encountered an interesting — and quite disruptive — behavior in a High Availability (HA) setup. Situation Overview When restoring a configuration on one cluster node, the entire configuration of the other nodes was overwritten — including settings that are supposed to remain unique and unsynced, such as hostnames, management…
![]()

