Support migration of non-HA router to HA and reverse
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
John Schwarz |
Bug Description
Updating a legacy router to HA and vice versa succeeds on the server side, but the L3 agent does not support this operation.
A reasonable goal would be to require users to perform an upgrade as such:
neutron router-update <r> --admin-
neutron router-update <r> --ha=True
neutron router-update <r> --admin-
(This is the same upgrade procedure for distributed routers).
Reminder: Setting a router's admin-state to False essentially unschedules it. This means that in order to implement the legacy-to-HA upgrade we would not need any agent patches at all. Another reminder: The server side upgrade code is actually already merged and covered by unit tests. So, to close this bug, all we need is to remove the exception thrown when a user changes the HA flag, and to test that it actually works.
tags: | removed: vrrp |
Changed in neutron: | |
importance: | Undecided → Medium |
description: | updated |
Changed in neutron: | |
assignee: | nobody → John Schwarz (jschwarz) |
status: | New → In Progress |
description: | updated |
Changed in neutron: | |
assignee: | John Schwarz (jschwarz) → Assaf Muller (amuller) |
Changed in neutron: | |
assignee: | Assaf Muller (amuller) → John Schwarz (jschwarz) |
Changed in neutron: | |
assignee: | John Schwarz (jschwarz) → Assaf Muller (amuller) |
Changed in neutron: | |
assignee: | Assaf Muller (amuller) → John Schwarz (jschwarz) |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
I think it's a task for Kilo, isn't it?