Bug 1730759

Upstream commits:
- f732a1ab9c574c1c17858a84cf7d25f294dfb151
- 5e0d2837c64a12e573b80fff00cb91cdd86db9c2
- 821e1e54abcb5dd95c0c5efdab67dc7c0246a17b

Hi Lorenzo,
   I have some question about this feature.Can you please help explain them?Thanks!

1. Is this the only new command for it or is there any else command?
ovn-nbctl --wait=hv set NB_Global . options:controller_event=true

2.I saw the event can be showwed by the below command in SBDB.Will the event also appear in the log file or in the NBDB?
ovn-sbctl list controller_event

(In reply to haidong li from comment #2)
> Hi Lorenzo,
>    I have some question about this feature.Can you please help explain
> them?Thanks!
> 
> 1. Is this the only new command for it or is there any else command?
> ovn-nbctl --wait=hv set NB_Global . options:controller_event=true
> 

correct

> 2.I saw the event can be showwed by the below command in SBDB.Will the event
> also appear in the log file or in the NBDB?
> ovn-sbctl list controller_event

events are created in controller_event table whenever ovn-controller receives a particular packet from ovs-vswitchd
(e.g. the ovn-controller receives a packet for a VIP with no back-end devices).
The CMS will monitor Controller_event table in order to 'reply' to the particular event occurred

Hi Lorenzo,does this feature support UDP and other ip packets,or just be effective when receive tcp packets?Thanks!

Verified on the latest version:
[root@dell-per730-19 opt]# uname -a
Linux dell-per730-19.rhts.eng.pek2.redhat.com 3.10.0-1061.el7.x86_64 #1 SMP Thu Jul 11 21:02:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@dell-per730-19 opt]# rpm -qa | grep openvswitch
kernel-kernel-networking-openvswitch-ovn-1.0-130.noarch
openvswitch-selinux-extra-policy-1.0-13.el7fdp.noarch
openvswitch2.11-2.11.0-18.el7fdp.x86_64
[root@dell-per730-19 opt]# rpm -qa | grep ovn
kernel-kernel-networking-openvswitch-ovn-1.0-130.noarch
ovn2.11-central-2.11.0-26.el7fdp.x86_64
ovn2.11-2.11.0-26.el7fdp.x86_64
ovn2.11-host-2.11.0-26.el7fdp.x86_64
[root@dell-per730-19 opt]# 
[root@dell-per730-19 opt]# ovn-nbctl list load_balancer
_uuid               : 0d3a7dcc-a162-4f9c-a2cd-8a1eec113ee0
external_ids        : {}
name                : "lb0"
protocol            : tcp
vips                : {"172.16.13.100:80"="", "172.16.13.200"="", "172.16.13.200:80"=""}

[root@dell-per730-19 opt]# ovn-sbctl list controller_even
_uuid               : 6b340d64-ff44-4b44-a8ca-53721bc59db8
chassis             : []
event_info          : {load_balancer="db75bf6a-3a99-44ac-9c73-95a8ff3cbd73", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 1

_uuid               : 0a2f21e0-caab-48eb-8715-9abb58514cb9
chassis             : 2a8a2e31-a530-4f2a-b628-fb10b448644e
event_info          : {load_balancer="db75bf6a-3a99-44ac-9c73-95a8ff3cbd73", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 1

_uuid               : 56a735a1-017c-425f-bad5-8425fd28b962
chassis             : 2a8a2e31-a530-4f2a-b628-fb10b448644e
event_info          : {load_balancer="0d3a7dcc-a162-4f9c-a2cd-8a1eec113ee0", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 2
[root@dell-per730-19 opt]# 

send tcp packet from remote:
[root@localhost ~]# nc 172.16.13.200 80   < 1.txt
05:22:00.280235 00:de:ad:01:00:01 > 00:de:ad:ff:01:02, ethertype IPv4 (0x0800), length 74: 172.16.102.11.40146 > 172.16.13.200.80: Flags [S], seq 2212248148, win 29200, options [mss 1460,sackOK,TS val 95442735 ecr 0,nop,wscale 7], length 0

05:22:01.281051 00:de:ad:01:00:01 > 00:de:ad:ff:01:02, ethertype IPv4 (0x0800), length 74: 172.16.102.11.40146 > 172.16.13.200.80: Flags [S], seq 2212248148, win 29200, options [mss 1460,sackOK,TS val 95443736 ecr 0,nop,wscale 7], length 0

local:
[root@dell-per730-19 opt]# ovn-sbctl list controller_even
_uuid               : 6b340d64-ff44-4b44-a8ca-53721bc59db8
chassis             : []
event_info          : {load_balancer="db75bf6a-3a99-44ac-9c73-95a8ff3cbd73", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 1

_uuid               : 0a2f21e0-caab-48eb-8715-9abb58514cb9
chassis             : 2a8a2e31-a530-4f2a-b628-fb10b448644e
event_info          : {load_balancer="db75bf6a-3a99-44ac-9c73-95a8ff3cbd73", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 1

_uuid               : 56a735a1-017c-425f-bad5-8425fd28b962
chassis             : 2a8a2e31-a530-4f2a-b628-fb10b448644e
event_info          : {load_balancer="0d3a7dcc-a162-4f9c-a2cd-8a1eec113ee0", protocol=tcp, vip="172.16.13.100:80"}
event_type          : empty_lb_backends
seq_num             : 2

_uuid               : 55daf377-87d8-4811-ac79-2c379cf5454a
chassis             : 2a8a2e31-a530-4f2a-b628-fb10b448644e
event_info          : {load_balancer="0d3a7dcc-a162-4f9c-a2cd-8a1eec113ee0", protocol=tcp, vip="172.16.13.200:80"}
event_type          : empty_lb_backends
seq_num             : 22
[root@dell-per730-19 opt]#

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-2019:2527