Public bug reported:
When we manually online an new l3 agent, after sync router info from
Neutron server, neutron-keepalived-state-change will always write
master in it's state file and notify other agents, even though there
still have an active ha router in other node.
====== Step to reproduce =======
1. stop neutron-l3-agent on node-A
2. create ha and distribute router test_router
3. we can see l3 agents hosting router info:
$ neutron l3-agent-list-hosting-router test_router
+--------------------------------------+------------+----------------+-------+----------+
| id | host | admin_state_up | alive |
ha_state |
+--------------------------------------+------------+----------------+-------+----------+
| 678cc6a6-3b28-462d-9374-4a7fb42193dc | compute1 | True | :-) |
standby |
| de274597-e35b-4ae5-baba-01c26bbed5b9 | compute2 | True | :-) |
active |
| 1c301ec4-9320-44e0-a4e0-a0441fee849a | network | True | :-) |
standby |
| 4ae490f7-8791-4460-8545-c172af58de8f | network2 | True | :-) |
standby |
+--------------------------------------+------------+----------------+-------+----------+
4. start neutron-l3-agent on node-A, after sync, we can see there are
two active ha routers in compute2 and node-A.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586058
Title:
Online an new neutron l3 agent, the router ha_state is active
Status in neutron:
New
Bug description:
When we manually online an new l3 agent, after sync router info from
Neutron server, neutron-keepalived-state-change will always write
master in it's state file and notify other agents, even though there
still have an active ha router in other node.
====== Step to reproduce =======
1. stop neutron-l3-agent on node-A
2. create ha and distribute router test_router
3. we can see l3 agents hosting router info:
$ neutron l3-agent-list-hosting-router test_router
+--------------------------------------+------------+----------------+-------+----------+
| id | host | admin_state_up | alive
| ha_state |
+--------------------------------------+------------+----------------+-------+----------+
| 678cc6a6-3b28-462d-9374-4a7fb42193dc | compute1 | True | :-)
| standby |
| de274597-e35b-4ae5-baba-01c26bbed5b9 | compute2 | True | :-)
| active |
| 1c301ec4-9320-44e0-a4e0-a0441fee849a | network | True | :-)
| standby |
| 4ae490f7-8791-4460-8545-c172af58de8f | network2 | True | :-)
| standby |
+--------------------------------------+------------+----------------+-------+----------+
4. start neutron-l3-agent on node-A, after sync, we can see there are
two active ha routers in compute2 and node-A.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586058/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
