Default external network stops working after adding another external network
Bug #1489718 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Python (Deprecated) |
Bug Description
MOS 6.1
Additional external network can be added following these instructions:
http://
Default network net04_ext is created without explicitly set --provider:network attribute, assuming L3 agent knows only one external bridge.
So after reconfiguring L3 agent it would not know that router-gateway interfaces of net04_ext should be plugged in br-floating (default ext bridge) and will plug them into br-int.
Workaround is to recreate net04_ext with proper parameters.
Changed in mos: | |
status: | New → Won't Fix |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
no longer affects: | mos/8.0.x |
Changed in mos: | |
status: | Won't Fix → Confirmed |
milestone: | none → 8.0 |
tags: | added: area-python |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 8.0 |
Changed in mos: | |
status: | Confirmed → Won't Fix |
assignee: | Fuel Python Team (fuel-python) → MOS Neutron (mos-neutron) |
status: | Won't Fix → Invalid |
tags: | added: covered-by-bp |
no longer affects: | mos |
no longer affects: | mos/6.1.x |
no longer affects: | mos/7.0.x |
To post a comment you must log in.
Eventhough it affects 6.1, there's nothing that could be done on MOS side.
It's fuel, so I'm not sure we can/should fix that for 6.1
Since we're not fixing it for 7.0, the only thing we can do is to target this to 8.0