yahoo-eng-team team mailing list archive

[Yoni <yshafrir@xxxxxxxxxx>]

Public bug reported:

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

For reference removal of a router from the same agent does yield a REST
error:

[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)

** Affects: neutron
     Importance: Undecided
     Assignee: Yoni (yshafrir)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Yoni (yshafrir)

-- 
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:
  Scheduling a router(HA/legacy) to an agent already scheduled for that
  router yields a success message

Status in OpenStack Neutron (virtual network service):
  New

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

  For reference removal of a router from the same agent does yield a
  REST error:

  [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)

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