When a router is active on only one network node and if the network node goes down by any reason, router still shows active status in controller
neutron l3-agent-list-hosting-router e5bae5bd-40ae-45b2-837d-9d00a74a1e1b
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
+--------------------------------------+--------------+----------------+-------+----------+
| id | host | admin_state_up | alive | ha_state |
+--------------------------------------+--------------+----------------+-------+----------+ |
| db94053c-f7a7-4bf8-a7ed-aa01f7c8ef34 | netowkr-node1| True | xxx | active |
+--------------------------------------+--------------+----------------+-------+----------+
Logic at https://github.com/openstack/neutron/blob/master/neutron/db/l3_hamode_db.py#L578, checks to update status based on dead agents, needs to executed in this scenario too.
Versioned github link from bug description: https:/ /github. com/openstack/ neutron/ blob/7bd521e7ce 1c4ffe5b65aad12 f3a1c1394c55473 /neutron/ db/l3_hamode_ db.py#L578
Adding a case for the scenario described in the bug description will fix the issue but is it HA if you only have one node? "an HA cluster is a two-node cluster, since that is the minimum required to provide redundancy" https:/ /en.wikipedia. org/wiki/ High-availabili ty_cluster
I think the bug can be reworded to exit HA mode if only one network node is detected, unless you have a use case for this?