yahoo-eng-team team mailing list archive

[Mike Kolesnik <mkolesni@xxxxxxxxxx>]

Public bug reported:

HA routers get scheduled automatically to L3 agents, you can view the
router using l3-agent-list-hosting-router

$ neutron l3-agent-list-hosting-router harouter2
+--------------------------------------+------+----------------+-------+
| id                                   | host | admin_state_up | alive |
+--------------------------------------+------+----------------+-------+
| 9c34ec17-9045-4744-ae82-1f65f72ce3bd | net1 | True           | :-)   |
| cf758b1b-423e-44d9-ab0f-cf0d524b3dac | net2 | True           | :-)   |
| f2aac1e3-7a00-47c3-b6c9-2543d4a2ba9a | net3 | True           | :-)   |
+--------------------------------------+------+----------------+-------+

You can remove it from an agent using l3-agent-router-remove, but when using l3-agent-router-add you get a 409:
$ neutron l3-agent-router-add bff55e85-65f6-4299-a3bb-f0e1c1ee2a05 harouter2
Conflict (HTTP 409) (Request-ID: req-22c1bb67-f0f8-4194-b863-93b8bb561c83)

The log says:
2014-12-10 07:47:41.036 INFO neutron.api.v2.resource [req-22c1bb67-f0f8-4194-b863-93b8bb561c83 admin f1bb80396ef34197b30117dfef45bea8] create failed (client error): The router 72b9f897-b84d-4270-a645-af38fe3bd838 has been already hosted by the L3 Agent 9c34ec17-9045-4744-ae82-1f65f72ce3bd.

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


** Tags: ha l3agent router scheduling

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

Title:
  HA router can't be manually scheduled on L3 agent

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  HA routers get scheduled automatically to L3 agents, you can view the
  router using l3-agent-list-hosting-router

  $ neutron l3-agent-list-hosting-router harouter2
  +--------------------------------------+------+----------------+-------+
  | id                                   | host | admin_state_up | alive |
  +--------------------------------------+------+----------------+-------+
  | 9c34ec17-9045-4744-ae82-1f65f72ce3bd | net1 | True           | :-)   |
  | cf758b1b-423e-44d9-ab0f-cf0d524b3dac | net2 | True           | :-)   |
  | f2aac1e3-7a00-47c3-b6c9-2543d4a2ba9a | net3 | True           | :-)   |
  +--------------------------------------+------+----------------+-------+

  You can remove it from an agent using l3-agent-router-remove, but when using l3-agent-router-add you get a 409:
  $ neutron l3-agent-router-add bff55e85-65f6-4299-a3bb-f0e1c1ee2a05 harouter2
  Conflict (HTTP 409) (Request-ID: req-22c1bb67-f0f8-4194-b863-93b8bb561c83)

  The log says:
  2014-12-10 07:47:41.036 INFO neutron.api.v2.resource [req-22c1bb67-f0f8-4194-b863-93b8bb561c83 admin f1bb80396ef34197b30117dfef45bea8] create failed (client error): The router 72b9f897-b84d-4270-a645-af38fe3bd838 has been already hosted by the L3 Agent 9c34ec17-9045-4744-ae82-1f65f72ce3bd.

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