Forum Discussion
drugovm_149811
Nimbostratus
When you run touch /service/mcpd/forceload and reboot second unit that is not getting sync you might lose you last changes that you made on the primary unit
Happened to me for few times. I can't wait for hotfix
clesan201305_11
Apr 16, 2014Nimbostratus
Unfortunately we were informed a hotfix is not coming for this, as F5 has an internally documented valid workaround in the use of set-sync-leader. This does not always resolve it for us. They state it will be fixed in the next major release (12, but could not give an ETA).
We have a way to reproduce it in a way that setting config-sync will break the configuration beyond repair of set-sync-leader (link the broken unit to an enterprise manager, create an analytics profile and watch the cluster crumble), and wanted to escalate the case. Unfortunately, F5 requires proof before they will escalate (mainly a qkview after setting sync leader failed), and we cannot continue bringing the customer's cluster down for this, so we have put this on hold for a while.
I do not have time to reproduce the issue in a lab environment for at least a few weeks. If someone else does, escalating to get a hotfix would help a lot of people out.