Description of problem: This is a failure in CI during installation. Installation doesn't complete because networking fails to come up because $SUBJECT. Job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-ovn/1470697722712428544. All logs are available in Artifacts. A specific log of potential interest to start: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-ovn/1470697722712428544/artifacts/e2e-openstack-ovn/gather-extra/artifacts/pods/openshift-ovn-kubernetes_ovnkube-master-rhjtx_ovn-dbchecker.log contains: F1214 11:42:04.051986 1 ovndbmanager.go:58] SBDB Upgrade failed: %!w(*fmt.wrapError=&{failed to get schema version for NBDB, stderr: "ovsdb-client: transaction returned error: {\"details\":\"get_schema request specifies database OVN_Southbound which is not yet available because it has not completed joining its cluster\",\"error\":\"database not available\"}\n", error: OVN command '/usr/bin/ovsdb-client -t 10 get-schema-version unix:/var/run/ovn/ovnsb_db.sock OVN_Southbound' failed: exit status 1 0xc000934c40}) Version-Release number of selected component (if applicable): 4.10 How reproducible: This job is extremely flaky, and looking at the last few failures this doesn't seem to be a common cause.
We'll continue to look out for it in CI, but unfortunately it's not something we can reproduce on demand. The problem does look like the one referenced, though. Do you want to just mark this one a duplicate?
*** This bug has been marked as a duplicate of bug 2022144 ***