Comment 7 for bug 2059721

I reinstalled host OS and rebuild it from scratch including all containers.
I reinstalled compute nodes one by one, not to overload OpenStack Infrastructure.
I'm using venv_wheel_build_enable=False to get around.
Alternative can be to reinstall and rebuild only infra (repo, galera, rabbitmq) on one controller, then rebuild compute nodes one by one with limit, then come back and finish first controller.
btw glusterfs on repo needs to be upgraded to 10 before rebuilding first repo server.
Also imo more services (not just keystone) do not support limit with recent releases.

Question: You said "you need to restart ovn-northd service and ovn-central right after it"
Why "right after it" is significant?

It seems to me I did restarted services "right after it".

I aslo restarted it after I completed upgrade of all controllers and the day after :)

After restarting ovn-northd I only see ovn-northd. 2 ovsdb-server are not started.
According ovn docs that the only thing is needed to finish ovn upgrade.
But you also restarted ovn-central.
Me too. otherwise ovsdb-servers will stay down.