error messages in ovn-controller when svc template is enabled

[cathy-zhou]

When svc template is enabled, and in the case the numberso f nodeIPs are different from multiple nodes, we saw the following ovn-controller error messages on the nodes with less IPS:

2024-04-16T21:39:43.768Z|03064|socket_util|ERR|NODEIP_IPv4_1:32358: bad IP address "NODEIP_IPv4_1" 2024-04-16T21:39:43.768Z|03065|socket_util|ERR|NODEIP_IPv4_1:31509: bad IP address "NODEIP_IPv4_1" 2024-04-16T21:39:43.768Z|03066|socket_util|ERR|NODEIP_IPv4_2:31509: bad IP address "NODEIP_IPv4_2" ... 2024-04-16T21:39:43.769Z|03068|lflow|WARN|error parsing match "ct.new && !ct.rel && ip4 && ip4.dst == ^NODEIP_IPv4_2 && tcp && tcp.dst == 31825": Syntax error at `NODEIP_IPv4_2' expecting constant.

The error messages may just be annoying and do no harm based on the ovn-nb(1M):

       If a template variable is referenced on a chassis for which that  vari‐
       able  is  not  defined then ovn-controller running on that chassis will
       just interpret it as a raw string literal.

But there are too many such log messages and it could pollute the logs and affect the other logs that are useful.

[tssurya]

OH I see if there are secondary IPs only on some nodes the other nodes are printing these logs that cause noise?

[trozet]

@dceara @numansiddique FYI

[dceara]

@trozet @cathy-zhou You're right, we should fix this in OVN. I opened an issue to track this: https://issues.redhat.com/browse/FDP-607

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.