Is this a regression if bug 1717461 was fixed in 4.3?

Branch that adds SCTP load balancing for OVN:

https://github.com/putnopvut/ovn/tree/sctp_lb

However, it does not add SCTP health checks, so turning health checks on for SCTP load balancers will likely result in bad things happening.

I have updated my branch linked in my previous comment. I've also now submitted a patch for inclusion in upstream OVN: https://mail.openvswitch.org/pipermail/ovs-dev/2020-March/368654.html

Tim, can you test my code with the ovn-kubernetes changes you've made to ensure that this is working as expected? Just to re-iterated, health checks are not supported for SCTP load balancers. So if you attempt to configured a health check for an SCTP load balancer, you'll see a warning in the northd log and the health check will not be used.

I have a PR up on github. Now I can test your patch Mark. Will report back.

Mark I'm seeing the load balancer is there:
_uuid               : 69a2ee26-1086-42b6-a4f9-1b880cd047d7
external_ids        : {k8s-cluster-lb-sctp=yes}
health_check        : []
ip_port_mappings    : {}
name                : ""
protocol            : sctp
vips                : {"10.101.165.35:62324"="10.244.0.5:62324"}

But sctp traffic doesn't seem to be working via the load balancer. It does work directly between the pods though. Will take a closer look on Monday.

FYI see https://bugzilla.redhat.com/show_bug.cgi?id=1718372#c8 for latest update on testing.

This landed in https://github.com/openshift/ovn-kubernetes/pull/123

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-2020:2409