L3 application does not take care of allowed address pairs
Bug #1712503 reported by
Irena Berezovsky
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
Fix Released
|
High
|
Dima Kuznetsov | ||
Bug Description
With Octavia integration LoadBalancer is running inside Amphora VM and VIP is added in allowed-address pairs of the Amphora port. Dragonflow L3 app does not install the flows properly to enable routing to the VIP (to the address in the allowed-address pairs)
| Changed in dragonflow: | |
| assignee: | nobody → Dima Kuznetsov (dimakuz) |
| importance: | Undecided → Medium |
| importance: | Medium → High |
| status: | New → Confirmed |
| Changed in dragonflow: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to dragonflow (master) | #1 |
| Changed in dragonflow: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit d9cd3e60af91f3e
Author: Dima Kuznetsov <email address hidden>
Date: Wed Aug 23 11:38:42 2017 +0300
Add allowed address pairs to L3 proactive routing
Closes-Bug: #1712503
Change-Id: I37edb9f755fb0a