Loadbalancer missing logical switch association
Bug #1794260 reported by
Luis Tomas Bolivar
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When a port (P1) in a Subnet (S1) tries to reach a member (P2 on S2) of a loadbalancer (LB1) through the loadbalancer VIP (P3 on S3), the traffic gets lost in it's way back from the member (P2) to the caller (P1).
The problem raises from the loadbalancer not being associated to the caller's subnet switch. For instance, the next command with make the request successful:
ovn-nbctl set logical_switch S1_logical_
Changed in networking-ovn: | |
assignee: | nobody → Reedip (reedip-banerjee) |
Changed in networking-ovn: | |
status: | New → In Progress |
tags: | added: networking-ovn-proactive-backport-potential |
To post a comment you must log in.
As per the discussion with Numan yesterday, an ideal way to handle the above issue might be to track the changes in a router.
- Use case #1: Members, VIPs and user are in the same subnet
- Use case #2: Network 1 and Network 2 are created , followed by router.After that LB is created on Network 1, Network 1 has VIP, Network 2 has Member and User putting the Curl Request.
- Use case #3: Network 1 followed by router.After that LB is created on Network 1, Network 1 has VIP. Network 2 is now created, connected to the router . Network 2 now has a Member for the VIP. User can be on Network 1/Network 2.
- Use case #4: Network 1 followed by router.After that LB is created on Network 1, Network 1 has VIP. Network 2 is now created, connected to the router . Network 2 now has a Member for the VIP. Network 3 is now created and connected to the router. Network 3 has the User for the curl request.
In Use Case 2-4 , router will know about all the changes in the network, so it would be easier if we can track all the networks associated to a router. In case a network has a LB and is associated with a new router, the LB can be associated with the router and any NEW network connected to the router.
NOTE: the same process has to be considered if the network interfaces are removed from a router :)