[OVSDB-475] extra ipv6 controller incorrectly configured Created: 04/Jan/19  Updated: 16/Jan/19  Resolved: 16/Jan/19

Status: Resolved
Project: ovsdb
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Low
Reporter: Vishal Thapar Assignee: Vishal Thapar
Resolution: Done Votes: 0
Labels: IPV6
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

While testing fix for OVSDB-466 in a proper deployment, it was noticed that an extra controller is being configured.

Manager "tcp:[fd00:fd00:fd00:2000::20]:6640"
is_connected: true
Manager "tcp:[fd00:fd00:fd00:2000::28]:6640"
is_connected: true
Manager "tcp:[fd00:fd00:fd00:2000::1e]:6640"
is_connected: true
Manager "ptcp:6639:[::1]"
Bridge br-int
Controller "tcp:[fd00:fd00:fd00:2000::1e]:6653"
is_connected: true
Controller "tcp:[fd00:fd00:fd00:2000::20]:6653"
is_connected: true
Controller "tcp:fd00:fd00:fd00:2000:0:0:0:20:6653"
Controller "tcp:[fd00:fd00:fd00:2000::28]:6653"
is_connected: true
fail_mode: secure

There is a correct entry for this IP already present and everything works fine. But this wrong entry fills up OVS logs with repeated connection attempts and failures which makes troubleshooting difficult.

 Comments   
Comment by Vishal Thapar [ 08/Jan/19 ]

If a ptcp manager is set on OVS, we configure controller through connection info. There are two issues with this code today:

1. Doesn't work well for IPv6.
2. Doesn't check if connection is to same port as configured in ptcp manager.

So we end up with an improper controller configured based on ptcp even if we already configured correct ones from manager entries.

Generated at Wed Feb 07 20:36:30 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.