Description of problem: This is seen with ovn2.13-20.12.0-20. bt (gdb) bt #0 0x00007fc2cad7670f in raise () from /lib64/libc.so.6 #1 0x00007fc2cad60b25 in abort () from /lib64/libc.so.6 #2 0x00005613f7c76654 in ovs_abort_valist () #3 0x00005613f7c7e444 in vlog_abort_valist () #4 0x00005613f7c7e4ea in vlog_abort () #5 0x00005613f7c7636b in ovs_assert_failure () #6 0x00005613f7b9684a in binding_seqno_run () #7 0x00005613f7b90aa9 in main () Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fix posted for review upstream: http://patchwork.ozlabs.org/project/ovn/patch/1613666578-23685-1-git-send-email-dceara@redhat.com/
Hi Dumitru, Is there reproducer for the crash?
(In reply to Jianlin Shi from comment #6) > Hi Dumitru, Hi Jianlin, > > Is there reproducer for the crash? Unfortunately, no. The window to reproduce the crash is quite narrow as it requires an OVSDB transaction towards the local OVS DB to still be in progress when a logical port is removed from the Southbound DB. The only way I could reproduce the crash was by instrumenting the ovn-controller code. I guess it would be ideal if we could do a smoke test of the whole functionality of the RFE in bug 1839102. Thanks, Dumitru
We ran the tests from bug 1839102 by repeatedly adding 100 lsp or modifying the db. The result is good and we didn't see coredump. [root@netqe20 ~]# rpm -qa | egrep "ovn|openv" ovn2.13-20.12.0-22.el8fdn.x86_64 ovn2.13-central-20.12.0-22.el8fdn.x86_64 openvswitch2.13-2.13.0-79.5.el8fdp.x86_64 ovn2.13-host-20.12.0-22.el8fdn.x86_64 openvswitch-selinux-extra-policy-1.0-28.el8fdp.noarch Attaching the test script and output. Thanks.
Created attachment 1762395 [details] The test script and output
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 (ovn2.13 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-2021:0839