Description of problem: Tracking issue for OVN-Kubernetes Active/Active HA using Raft. Development still in progress Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-08-094604 How reproducible: Always Steps to Reproduce: 1. configure networkType: "OVNKubernetes" 2. oc get pods -n openshift-ovn-kubernetes 3. Actual results: only one ovnkube-master pod Expected results: more than one ovnkube-master pod for Raft Additional info:
https://github.com/openshift/cluster-network-operator/pull/376
Overall OVN HA is not enabled right now, including Active/Standby.
PR 376 was merged, CI build registry.svc.ci.openshift.org/ocp/release:4.3.0-0.ci-2019-11-11-162924 deployed with three masters so it looks like we can test. $ oc get pods -n openshift-ovn-kubernetes NAME READY STATUS RESTARTS AGE ovnkube-master-62sfk 4/4 Running 0 145m ovnkube-master-8gpzc 4/4 Running 0 144m ovnkube-master-9rzpp 4/4 Running 0 144m
Verified this bug according to comment 3.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062