We have a 20 seconds timeout for configmap changes to be applied https://github.com/openshift/release/blob/master/ci-operator/step-registry/ovn/conf/turn-on-hybrid/ovn-conf-turn-on-hybrid-commands.sh#L13
Seems like it may not be enough, because the jobs are failing on that https://search.ci.openshift.org/?search=Timeout+waiting+for+the+ovn-kubernetes+config+map+to+update&maxAge=336h&context=1&type=bug%2Bissue%2Bjunit&name=e2e-aws-ovn-windows&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
but from the logs it seems like everything works fine, just slower that we expect?

Example jobs 
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/1631/pull-ci-openshift-ovn-kubernetes-release-4.13-e2e-aws-ovn-windows/1648710662072832000
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/1630/pull-ci-openshift-ovn-kubernetes-release-4.13-e2e-aws-ovn-windows/1645492291864891392
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/38149/rehearse-38149-pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-windows/1647936941204705280

1.
2.
3.