[ovs-dev] LSP requested-chassis not working as expected

[Marcin Mirecki]

Hi

I am trying to use the OVN LSP requested-chassis feature, but I it does not
work as expected.

I have a LogicalSwitchPort that is bound to two OVS Interfaces via
Interface:external_ids:iface, each Iterface on a different host.
The LSP is configured correctly, as each of the Interfaces has connectivity
when the others external_ids:iface property is removed.

When both have the external_ids:iface property set, only one of the
interfaces has connectivity.
I would expect that when I set the LogicalSwitchPort
options:requested-chassis to the name of the other chassis, the second
interface will have connectivity, but this does not happen (ovs-sbctl shows
the binding moved to the other host correctly, the log seems to confirm
that too).
Even when I set the value of options:requested-chassis to garbage, the
Interface on the first host still has connectivity (ovs-sbctl does not show
the binding on any of the hosts then).

Is this how LogicalSwitchPort options:requested-chassis should work, or am
I using it incorrectly?

More details attached below.

Thanks,
Marcin





## VERSION ##
> yum info openvswtich:
Installed Packages
Name        : openvswitch
Arch        : x86_64
Version     : 2.9.0
Release     : 8.el7fdn

Name        : openvswitch-ovn-central
Version     : 2.9.0

On hosts:
Name        : openvswitch-ovn-host
Version     : 2.9.0



## Changing of "options:requested-chassis" value ##

# ovn-sbctl show
Chassis "f0879d4e-334b-4ea0-8767-2571949b8f0c"
    hostname: "lago-basic-suite-master-host-1.lago.local"
    Encap geneve
        ip: "192.168.201.3"
        options: {csum="true"}
    Port_Binding "b34d3e8d-0c44-43fc-88e9-d483136dc130"
Chassis "392b25ed-a523-4f82-86ff-aa7568170b61"
    hostname: "lago-basic-suite-master-host-0.lago.local"
    Encap geneve
        ip: "192.168.201.2"
        options: {csum="true"}
    Port_Binding "96d308b4-bdf6-4b99-b36f-30a7fde55d14"
    Port_Binding "664a27b6-7171-4af3-8f4c-4cc1cf7e25d9"

Interface on host0 "392b25ed-a523-4f82-86ff-aa7568170b61" can ping network

After doing:
 ovn-nbctl set Logical_Switch_Port 96d308b4-bdf6-4b99-b36f-30a7fde55d14
options:requested-chassis="f0879d4e-334b-4ea0-8767-2571949b8f0c"

(both interfaces on the 2 hosts have the same mac, so it does not need to
be changed.

I have:

# ovn-sbctl show
Chassis "f0879d4e-334b-4ea0-8767-2571949b8f0c"
    hostname: "lago-basic-suite-master-host-1.lago.local"
    Encap geneve
        ip: "192.168.201.3"
        options: {csum="true"}
    Port_Binding "b34d3e8d-0c44-43fc-88e9-d483136dc130"
    Port_Binding "96d308b4-bdf6-4b99-b36f-30a7fde55d14"
Chassis "392b25ed-a523-4f82-86ff-aa7568170b61"
    hostname: "lago-basic-suite-master-host-0.lago.local"
    Encap geneve
        ip: "192.168.201.2"
        options: {csum="true"}
    Port_Binding "664a27b6-7171-4af3-8f4c-4cc1cf7e25d9"

so the binding moved to the other host, but stil only the interface on
host0 "392b25ed-a523-4f82-86ff-aa7568170b61" can ping network.



## LOGS ##

Not attaching whole log file due to size = 250MB

Host0 has log entries like (ovn-controller.log):

2018-03-16T10:09:31.442Z|00059|binding|INFO|Claiming lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 for this chassis.
2018-03-16T10:09:31.442Z|00060|binding|INFO|96d308b4-bdf6-4b99-b36f-30a7fde55d14:
Claiming 02:01:00:00:02:02 12.0.0.3
2018-03-16T10:09:34.053Z|00061|binding|INFO|Changing chassis for lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 from
f0879d4e-334b-4ea0-8767-2571949b8f0c to
392b25ed-a523-4f82-86ff-aa7568170b61.
2018-03-16T10:09:34.053Z|00062|binding|INFO|96d308b4-bdf6-4b99-b36f-30a7fde55d14:
Claiming 02:01:00:00:02:02 12.0.0.3

2018-03-16T13:10:16.206Z|00022|binding|INFO|Changing chassis for lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 from
f0879d4e-334b-4ea0-8767-2571949b8f0c to
392b25ed-a523-4f82-86ff-aa7568170b61.
2018-03-16T13:10:16.206Z|00023|binding|INFO|96d308b4-bdf6-4b99-b36f-30a7fde55d14:
Claiming 02:01:00:00:02:02 dynamic
2018-03-16T13:10:16.208Z|00024|binding|INFO|Claiming lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 for this chassis.
2018-03-16T13:10:16.208Z|00025|binding|INFO|96d308b4-bdf6-4b99-b36f-30a7fde55d14:
Claiming 02:01:00:00:02:02 dynamic
2018-03-16T13:10:32.688Z|00026|binding|INFO|Releasing lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 from this chassis.

2018-03-16T15:20:54.058Z|01066|binding|INFO|Not claiming lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14, chassis
392b25ed-a523-4f82-86ff-aa7568170b61 requested-chassis
f0879d4e-334b-4ea0-8767-2571949b8f0c


Host1 (ovn-controller.log):

2018-03-16T13:10:16.200Z|00022|binding|INFO|Releasing lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 from this chassis.

2018-03-16T15:07:29.215Z|00127|binding|INFO|Not claiming lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14, chassis
f0879d4e-334b-4ea0-8767-2571949b8f0c requested-chassis
392b25ed-a523-4f82-86ff-aa7568170b61

2018-03-16T13:10:32.685Z|00028|binding|INFO|Claiming lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 for this chassis.

2018-03-16T10:41:06.681Z|1660044|binding|INFO|Changing chassis for lport
96d308b4-bdf6-4b99-b36f-30a7fde55d14 from
392b25ed-a523-4f82-86ff-aa7568170b61 to
f0879d4e-334b-4ea0-8767-2571949b8f0c.