Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1913162

Summary: [OVN] Wrong log message "|WARN|handle service check: Unsupported protocol - [11]" for udp load_balancer healthe check
Product: Red Hat Enterprise Linux Fast Datapath Reporter: ying xu <yinxu>
Component: ovn2.13Assignee: OVN Team <ovnteam>
Status: CLOSED WONTFIX QA Contact: ying xu <yinxu>
Severity: medium Docs Contact:
Priority: medium    
Version: FDP 21.ACC: ctrautma, dceara, jishi, mmichels, ralongi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-29 20:30:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description ying xu 2021-01-06 07:23:29 UTC
Description of problem:
[OVN] Wrong log message "|WARN|handle service check: Unsupported protocol - [11]" for udp load_balancer healthe check

Version-Release number of selected component (if applicable):
# rpm -qa|grep ovn
ovn2.13-20.12.0-1.el8fdp.x86_64
ovn2.13-host-20.12.0-1.el8fdp.x86_64
ovn2.13-central-20.12.0-1.el8fdp.x86_64

How reproducible:
always

Steps to Reproduce:
1.add udp load_balancer and healthe check for it
2.check the ovn-controller.log, there are WARN "handle service check: Unsupported protocol"
3.but the unsupported protocol is sctp ,not udp.

script:
               ovn-nbctl lr-add r1
                ovn-nbctl lrp-add r1 r1_s2 00:de:ad:ff:01:02 172.16.102.1/24 2001:db8:102::1/64
                ovn-nbctl lrp-add r1 r1_s3 00:de:ad:ff:01:03 172.16.103.1/24 2001:db8:103::1/64

                # s2
                ovn-nbctl ls-add s2
                ovn-nbctl set Logical-switch s2 other_config:subnet=172.16.102.0/24
                ovn-nbctl set Logical-switch s2 other_config:ipv6_prefix=2001:db8:102::0

                # s2 - r1
                ovn-nbctl lsp-add s2 s2_r1
                ovn-nbctl lsp-set-type s2_r1 router
                ovn-nbctl lsp-set-addresses s2_r1 "00:de:ad:ff:01:02 172.16.102.1 2001:db8:102::1"
                ovn-nbctl lsp-set-options s2_r1 router-port=r1_s2

                # s2 - hv1_vm00_vnet1
                ovn-nbctl lsp-add s2 vm10
                ovn-nbctl lsp-set-addresses vm10 "00:de:ad:01:00:01 172.16.102.11 2001:db8:102::11"

                # s2 - hv1_vm01_vnet1
                ovn-nbctl lsp-add s2 vm11
                ovn-nbctl lsp-set-addresses vm11 "00:de:ad:01:01:01 172.16.102.12 2001:db8:102::12"
		# s3
                ovn-nbctl ls-add s3
                ovn-nbctl set Logical-switch s3 other_config:subnet=172.16.103.0/24
                ovn-nbctl set Logical-switch s3 other_config:ipv6_prefix=2001:db8:103::0

                # s3 - r1
                ovn-nbctl lsp-add s3 s3_r1
                ovn-nbctl lsp-set-type s3_r1 router
                ovn-nbctl lsp-set-addresses s3_r1 "00:de:ad:ff:01:03 172.16.103.1 2001:db8:103::1"
                ovn-nbctl lsp-set-options s3_r1 router-port=r1_s3

                # s3 - hv0_vm00_vnet1
                ovn-nbctl lsp-add s3 vm00
                ovn-nbctl lsp-set-addresses vm00 "00:de:ad:00:00:01 172.16.103.11 2001:db8:103::11"

                # s3 - hv0_vm01_vnet1
                ovn-nbctl lsp-add s3 vm01
                ovn-nbctl lsp-set-addresses vm01 "00:de:ad:00:01:01 172.16.103.12 2001:db8:103::12"

		ip netns add vm10
                ovs-vsctl add-port br-int vm10 -- set interface vm10 type=internal
                ip link set vm10 netns vm10
                ip netns exec vm10 ip link set vm10 address 00:de:ad:01:00:01
                ip netns exec vm10 ip addr add 172.16.102.11/24 dev vm10
                ip netns exec vm10 ip link set vm10 up
                ip netns exec vm10 ip link set lo up
                ip netns exec vm10 ip route add default via 172.16.102.1
                ovs-vsctl set Interface vm10 external_ids:iface-id=vm10

		ip netns add vm11
                ovs-vsctl add-port br-int vm11 -- set interface vm11 type=internal
                ip link set vm11 netns vm11
                ip netns exec vm11 ip link set vm11 address 00:de:ad:01:01:01
                ip netns exec vm11 ip addr add 172.16.102.12/24 dev vm11
                ip netns exec vm11 ip link set vm11 up
                ip netns exec vm11 ip link set lo up
                ip netns exec vm11 ip route add default via 172.16.102.1
                ovs-vsctl set Interface vm11 external_ids:iface-id=vm11


                ovn-nbctl set  Logical_Router r1 options:chassis="hv1"

	
 
                ovn-nbctl  lb-add lb2 172.16.103.10:8000 172.16.103.12:80,172.16.102.12:80 udp
                uuid1=`ovn-nbctl --bare --columns _uuid find load_balancer name=lb2`
                ovn-nbctl --wait=sb set load_balancer $uuid1 ip_port_mappings:172.16.103.12=vm01:172.16.103.2
                ovn-nbctl --wait=sb set load_balancer $uuid1 ip_port_mappings:172.16.102.12=vm11:172.16.102.2
                uuid4=`ovn-nbctl --id=@hc create Load_Balancer_Health_Check vip="172.16.103.10\:8000" -- add Load_Balancer $uuid1 health_check @hc`
                ovn-nbctl set Load_Balancer_Health_Check $uuid4 options:interval=5 options:timeout=20 options:success_count=3 options:failure_count=3
		ovn-nbctl set logical_switch s2 load_balancer=$uuid1
                ovn-nbctl set logical_router r1 load_balancer=$uuid1
                ovn-nbctl set logical_switch s3 load_balancer=$uuid1


Actual results:
cat /var/log/ovn/ovn-controller.log|grep service.check'
2021-01-06T07:13:26.591Z|00004|pinctrl(ovn_pinctrl0)|WARN|handle service check: Unsupported protocol - [11]

Expected results:
no warn for udp lb

Additional info:

Comment 1 Dumitru Ceara 2023-05-30 09:45:51 UTC
Upstream patch that fixes this issue:

https://patchwork.ozlabs.org/project/ovn/patch/20230522211815.1201754-1-odivlad@gmail.com/

Comment 2 OVN Bot 2023-06-20 19:49:33 UTC
ovn22.03 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216310
ovn22.03 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216311
ovn22.12 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216312
ovn22.12 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216313
ovn23.03 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216316
ovn23.03 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216317
ovn23.06 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216320
ovn23.06 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216321
ovn22.06 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216324
ovn22.06 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216325
ovn22.09 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216326
ovn22.09 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2216327

Comment 3 Mark Michelson 2024-10-29 20:30:58 UTC
THis issue is being closed because it is one of three open OVN Bugzilla issues. If this issue is still a problem in modern OVN versions, please create a Jira issue.