Broken L3 HA migration should be blocked
Bug #1378525 reported by
Assaf Muller
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Akihiro Motoki | ||
Juno |
Fix Released
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
High
|
Assaf Muller |
Bug Description
While the HA property is update-able, and resulting router-get
invocations suggest that the router is HA, the migration
itself fails on the agent. This is deceiving and confusing
and should be blocked until the migration itself is fixed
in a future patch.
Changed in neutron: | |
assignee: | nobody → Assaf Muller (amuller) |
status: | New → In Progress |
Changed in neutron: | |
importance: | Undecided → High |
Changed in neutron: | |
milestone: | none → juno-rc3 |
tags: | removed: juno-rc-potential |
Changed in horizon: | |
assignee: | nobody → Akihiro Motoki (amotoki) |
Changed in horizon: | |
importance: | Undecided → Medium |
tags: | added: juno-rc-potential |
Changed in neutron: | |
milestone: | juno-rc3 → 2014.2 |
tags: |
added: juno-backport-potential removed: juno-rc-potential |
Changed in horizon: | |
milestone: | none → kilo-1 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
This affects Horizon router update form because the form supports to update 'ha' attribute in a router.
I am not sure at now whether the fix in Neutron will be shipped in Juno or not, and Horizon need to catch up the change at this last moment of the cycle.