I agree with Roman. The deployment must ensure none of the Openstack service instances in cluster are running then one's db is being synced. I suggest to:
1) For new deployments, make db sync at the very first (primary) controller only, and never do it on other nodes - then OSt services already deployed and running at the previousely deployed node(s).
2) For patching, stop all instances of Openstack service which db is about to be synced and start it once it is done
I agree with Roman. The deployment must ensure none of the Openstack service instances in cluster are running then one's db is being synced. I suggest to:
1) For new deployments, make db sync at the very first (primary) controller only, and never do it on other nodes - then OSt services already deployed and running at the previousely deployed node(s).
2) For patching, stop all instances of Openstack service which db is about to be synced and start it once it is done