-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Description:
ovn-northd would crash after create bfd
version:
ovn23.09-23.09.4-30
steps:
systemctl start openvswitch systemctl start ovn-northd ovn-nbctl set-connection ptcp:6641 ovn-sbctl set-connection ptcp:6642 ovs-vsctl set open . external_ids:system-id=hv1 external_ids:ovn-remote=tcp:20.0.86.25:6642 external_ids:ovn-encap-type=geneve external_ids:ovn-encap-ip=20.0.86.25 systemctl restart ovn-controller ovn-nbctl lr-add R2 ovn-nbctl set logical_router R2 options:chassis=hv1 ovn-nbctl ls-add join ovn-nbctl lrp-add R2 R2_join 00:00:04:01:02:04 20.0.0.2/24 4000::2/64 ovn-nbctl lsp-add join r2-join -- set Logical_Switch_Port r2-join \ type=router options:router-port=R2_join addresses='"00:00:04:01:02:04"' ovn-nbctl create bfd logical_port=R2_join dst_ip=20.0.0.5 min_tx=250 min_rx=250 detect_mult=10 sleep 5 cat /var/log/ovn/ovn-northd.log
expected result:
no crash
actual result:
ovn-northd crash:
2024-09-24T05:49:13.365Z|00003|vlog(monitor)|INFO|opened log file /var/log/ovn/ovn-northd.log
2024-09-24T05:49:13.365Z|00004|backtrace(monitor)|WARN|SIGSEGV detected, backtrace:
ovn-northd(+0x7a6f1) [0x55f7dd9e76f1]
/lib64/libc.so.6(+0x3e6f0) [0x7f951da3e6f0]
ovn-northd(+0x5dc8d) [0x55f7dd9cac8d]
ovn-northd(+0x668f8) [0x55f7dd9d38f8]
ovn-northd(+0x6a308) [0x55f7dd9d7308]
ovn-northd(+0x1bb7c) [0x55f7dd988b7c]
/lib64/libc.so.6(+0x29590) [0x7f951da29590]
/lib64/libc.so.6(__libc_start_main+0x80) [0x7f951da29640]
ovn-northd(+0x1cbc5) [0x55f7dd989bc5]
2024-09-24T05:49:13.365Z|00005|daemon_unix(monitor)|ERR|1 crashes: pid 161679 died, killed (Segmentation fault), core dumped, restarting
2024-09-24T05:49:13.368Z|00006|vlog(monitor)|INFO|closing log file
2024-09-24T05:49:13.368Z|00006|ovn_northd(ovn-northd)|INFO|OVN internal version is : [23.09.6-20.32.0-71.6]
[root@wsfd-advnetlab18 test]# rpm -qa | grep -E "openvswitch3.3|ovn23.09"
openvswitch3.3-3.3.0-49.el9fdp.x86_64
ovn23.09-23.09.4-30.el9fdp.x86_64
ovn23.09-central-23.09.4-30.el9fdp.x86_64
ovn23.09-host-23.09.4-30.el9fdp.x86_64
other info:
the problem didn't exist on 23.09.3-5, and started to occur since 23.09.3-39