During L->N upgrade, the floating ip connectivity is lost.
Bug #1698373 reported by
Sofer Athlan-Guyot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Sofer Athlan-Guyot |
Bug Description
Hi,
After a discussion with Miguel Angel Ajo, it seems that the cut in floating ip is not needed, ie downtime to the l3 agents shouldn't translate into floating ip unreachability. Full explanation here[1]
Changed in tripleo: | |
status: | Confirmed → Triaged |
assignee: | nobody → Sofer Athlan-Guyot (sofer-athlan-guyot) |
importance: | Critical → High |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
To post a comment you must log in.
Fix proposed to branch: stable/newton /review. openstack. org/474967
Review: https:/