CARP HA on VMware works with 19.1.7 / fails with 19.1.8

Started by katamadone [CH], June 03, 2019, 06:55:01 AM

Previous topic - Next topic
Actually today I tried to update from 19.1.7 to 19.1.8 but had to rollback because it looks like HA CARP is broken.
Anyone can test/confirm that:
- Both Firewalls installed with 19.1.7 configured HA and multiple CARP IPs on multiple interfaces
- Update secondary to 19.1.8 check functionality
- then "Enter persistent CARP Maintenance Mode" --> hand over CARP MASTER to SLAVE FW
- "Leave persistent CARP Maintenance Mode" --> to test if CARP still works
- "Enter persistent CARP Maintenance Mode" --> to handover CARP MASTER again in front of the update
- Update primary to 19.1.8 - all good so far inclusive the reboot.
- But now "Leave persistent CARP Maintenance Mode" will not handover back the MASTER CARP Role to the primary.

Actually I couldn't do more intensive testing and had to rollback.

You just have to reboot unit2 (current master), there was a change which affects some users preventing to release mnt mode. There is a second thread around here where I ask for sysctl values before/while/after maintainence.

If you are motivated search for it and post there so I can track this down.

Sorry I gave no answer. Same with 19.1.10. Try to track that down tomorrow. Same and eproducable?

--Switching to your other thread https://forum.opnsense.org/index.php?topic=12832.msg59655#msg59655