https://github.com/openshift/ose/pull/1215
cannot reproduce the problem in old version, and verified in atomic-openshift-3.9.27-1.git.0.964617d that the ovs flow has been updated as below: cookie=0xe216df8b, duration=30407.563s, table=10, n_packets=96649, n_bytes=19580171, priority=100,tun_src=10.240.0.10 actions=goto_table:30 cookie=0x6d3e6ac, duration=12016.153s, table=10, n_packets=6434, n_bytes=4920683, priority=100,tun_src=10.240.0.11 actions=goto_table:30 cookie=0xe216df8b, duration=30407.554s, table=50, n_packets=1237, n_bytes=51954, priority=100,arp,arp_tpa=10.130.0.0/16 actions=move:NXM_NX_REG0[]->NXM_NX_TUN_ID[0..31],set_field:10.240.0.10->tun_dst,output:1 cookie=0x6d3e6ac, duration=12016.135s, table=50, n_packets=163, n_bytes=6846, priority=100,arp,arp_tpa=10.129.0.0/16 actions=move:NXM_NX_REG0[]->NXM_NX_TUN_ID[0..31],set_field:10.240.0.11->tun_dst,output:1 cookie=0xe216df8b, duration=30407.548s, table=90, n_packets=97799, n_bytes=8442205, priority=100,ip,nw_dst=10.130.0.0/16 actions=move:NXM_NX_REG0[]->NXM_NX_TUN_ID[0..31],set_field:10.240.0.10->tun_dst,output:1 cookie=0x6d3e6ac, duration=12016.110s, table=90, n_packets=6851, n_bytes=893681, priority=100,ip,nw_dst=10.129.0.0/16 actions=move:NXM_NX_REG0[]->NXM_NX_TUN_ID[0..31],set_field:10.240.0.11->tun_dst,output:1 Each ovs flow for other node's IP has a random cookie now. Did some related regression test such as delete/add/reboot nodes and no issues found. OS: Red Hat Enterprise Linux Server release 7.5 (Maipo) Kernel: 3.10.0-862.el7.x86_64
> cannot reproduce the problem in old version Yeah, it's a race condition, and it might only happen when the nodes are slow/overloaded. FWIW, I did verify that the new unit test TestHostSubnetReassignment() *does* fail when run against the old ovscontroller.go code.
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-2018:1566