neutron-keepalived-state-change and keeplived cannot be cleanup for those routers which is deleted during l3-agent died
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned |
Bug Description
Pre-conditions:
deploy a 3 controller openstack cluster with stable/rocky branch without using docker, and enable l3 agent ha in configuration files: neutron.conf
l3_ha = true
max_l3_
reproduction steps:
1. create a router and wait for neutron-
2. stop the neutron-l3-agent on control-1, systemctl stop neutron-l3-agent
3. delete the router and wait for the process complete so that neutron router show <router_id> report the router is non-existed.
4. start the neutron-l3-agent again on control-1 until neutron agent-list reporting it alive
5. ps -ef | grep <router_id> , you will find neutron-
tags: | added: l3 |
tags: |
added: l3-dvr-backlog removed: l3 |
Hi,
Thanks for filing this bug. I have two questions:
1) What happens if you replicate the experiment only with two controllers? Do you see the same behavior
2) Is this something that happens in production? Or was this an experiment with devstack or a test bed?