Created attachment 1952418 [details] ovs-vswitchd journal at dbg lvl OVN-Kubernetes issue: https://issues.redhat.com/browse/OCPBUGS-10485 Description of problem: During OCP node startup network setup fails because DHCP packets are not leaving the node. It looks like there are no DP flows programmed: ovs-appctl dpctl/show system@ovs-system: lookups: hit:0 missed:620282 lost:620282 flows: 0 masks: hit:0 total:0 hit/pkt:0.00 caches: masks-cache: size:256 port 0: ovs-system (internal) port 1: ens4 port 2: ovn-k8s-mp0 (internal) port 3: genev_sys_6081 (geneve: packet_type=ptap) port 4: br-int (internal) port 5: br-ex (internal) ovs-ofctl dump-flows br-ex cookie=0x0, duration=171.388s, table=0, n_packets=5, n_bytes=210, priority=0 actions=NORMAL ovs-appctl dpctl/dump-flows <NO_OUTPUT> Version-Release number of selected component (if applicable): ovs_version: "3.1.1" OCP version: 4.13.0-0.nightly-2023-03-14-053612 How reproducible: Often, but only when using nodes with two cores Steps to Reproduce: Setup OCP 4.13.0-0.nightly-2023-03-14-053612 using workers that have 2 CPU cores each Actual results: ovs-configuration.service fails to setup br-ex, DHCP traffic not leaving the node Expected results: network setup succedes Additional info: Looking at the attached ovs-vswitchd it looks like there are initially 0 n-handler-threads configured
Based on the verification in https://issues.redhat.com/browse/OCPBUGS-10485 we are marking this as verified.
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 (openvswitch3.1 bug fix and enhancement update), 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-2023:3994