yahoo-eng-team team mailing list archive

[Doug Hellmann <doug@xxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1365426

Title:
  Support migration of non-HA router to HA and reverse

Status in neutron:
  Fix Released

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-state-up=False
  neutron router-update <r> --ha=True
  neutron router-update <r> --admin-state-up=True

  (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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1365426/+subscriptions