Public bug reported: As the title says, updating a non-HA router to be HA while there is less than the minimum available l3 agents to handle this router results in an invalid state caused by a partial update.
[stack@js16 ~]$ neutron router-create --ha=False x neutron router-update x --admin-0sCreated a new router: +-------------------------+--------------------------------------+ | Field | Value | +-------------------------+--------------------------------------+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | description | | | distributed | False | | external_gateway_info | | | ha | False | | id | 488a0eab-bf7a-4aea-84a4-4146a79eb225 | | name | x | | routes | | | status | ACTIVE | | tenant_id | 20482218062b458589b9cffa3a1bb172 | +-------------------------+--------------------------------------+ [stack@js16 ~]$ neutron router-update x --admin-state-up=False Updated router: x [stack@js16 ~]$ neutron router-update x --ha=True Not enough l3 agents available to ensure HA. Minimum required 2, available 1. Neutron server returns request_ids: ['req-4c5400c5-465e-419b-aeda-e637a76c29a1'] [stack@js16 ~]$ neutron router-show x +-------------------------+--------------------------------------+ | Field | Value | +-------------------------+--------------------------------------+ | admin_state_up | False | | availability_zone_hints | | | availability_zones | | | description | | | distributed | False | | external_gateway_info | | | ha | True | | id | 488a0eab-bf7a-4aea-84a4-4146a79eb225 | | name | x | | routes | | | status | ALLOCATING | | tenant_id | 20482218062b458589b9cffa3a1bb172 | +-------------------------+--------------------------------------+ [stack@js16 ~]$ neutron l3-agent-list-hosting-router x [stack@js16 ~]$ The router is set to HA and the status is stuck in ALLOCATING even though it wasn't scheduled to any agent. ** Affects: neutron Importance: Undecided Assignee: John Schwarz (jschwarz) Status: New ** Tags: l3-ha ** Changed in: neutron Assignee: (unassigned) => John Schwarz (jschwarz) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1609665 Title: Updating a router to HA without enough agents results in partial update Status in neutron: New Bug description: As the title says, updating a non-HA router to be HA while there is less than the minimum available l3 agents to handle this router results in an invalid state caused by a partial update. [stack@js16 ~]$ neutron router-create --ha=False x neutron router-update x --admin-0sCreated a new router: +-------------------------+--------------------------------------+ | Field | Value | +-------------------------+--------------------------------------+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | description | | | distributed | False | | external_gateway_info | | | ha | False | | id | 488a0eab-bf7a-4aea-84a4-4146a79eb225 | | name | x | | routes | | | status | ACTIVE | | tenant_id | 20482218062b458589b9cffa3a1bb172 | +-------------------------+--------------------------------------+ [stack@js16 ~]$ neutron router-update x --admin-state-up=False Updated router: x [stack@js16 ~]$ neutron router-update x --ha=True Not enough l3 agents available to ensure HA. Minimum required 2, available 1. Neutron server returns request_ids: ['req-4c5400c5-465e-419b-aeda-e637a76c29a1'] [stack@js16 ~]$ neutron router-show x +-------------------------+--------------------------------------+ | Field | Value | +-------------------------+--------------------------------------+ | admin_state_up | False | | availability_zone_hints | | | availability_zones | | | description | | | distributed | False | | external_gateway_info | | | ha | True | | id | 488a0eab-bf7a-4aea-84a4-4146a79eb225 | | name | x | | routes | | | status | ALLOCATING | | tenant_id | 20482218062b458589b9cffa3a1bb172 | +-------------------------+--------------------------------------+ [stack@js16 ~]$ neutron l3-agent-list-hosting-router x [stack@js16 ~]$ The router is set to HA and the status is stuck in ALLOCATING even though it wasn't scheduled to any agent. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1609665/+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