yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

** Changed in: neutron
    Milestone: None => kilo-3

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

Title:
  Unscheduling a router(HA/legacy) from an agent not scheduled for that
  router causes an error.

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:

  A legacy router was created and automatically scheduled to both agents.
  Given this state of the agent scheduling :

  [stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-list-hosting-router R5
  +--------------------------------------+-------------------------+----------------+-------+
  | id                                   | host                    | admin_state_up | alive |
  +--------------------------------------+-------------------------+----------------+-------+
  | fda97b55-813b-486e-8a74-e2c7aa830f52 | vpn-6-41.tlv.redhat.com | True           | :-)   |
  +--------------------------------------+-------------------------+----------------+-------+

  When trying to remove a router from the same agent twice an error
  occurs:

  [stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-router-remove fda97b55-813b-486e-8a74-e2c7aa830f52 R5
  Removed router R5 from L3 agent
  [stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-router-remove fda97b55-813b-486e-8a74-e2c7aa830f52 R5
  Conflict (HTTP 409) (Request-ID: req-9a96e8a2-70f8-4c24-b256-6dffb933282c)

  For reference, when trying to re-schedule the router on the same agent
  the client notifies the user:

  neutron l3-agent-router-add fda97b55-813b-486e-8a74-e2c7aa830f52 R5
  Added router R5 to L3 agent
  neutron l3-agent-router-add fda97b55-813b-486e-8a74-e2c7aa830f52 R5
  Added router R5 to L3 agent

  There is no 'real' effect on the DB or anything but the client should indicate the operation failed
  since the agent is already scheduled.

  The second removal of the same agent shouldn't fail as we try to avoid
  unnecessary errors.

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