Router with l3_agent state unknown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Incomplete
|
Undecided
|
Mohankumar |
Bug Description
❯ openstack network agent list --router r1 --long
+------
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+------
| 6faf003f-
| bf90fed6-
+------
❯ openstack network agent list --router r1 --long
+------
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary | HA State |
+------
| 6faf003f-
| bf90fed6-
+------
When neutron-server notices the l3_agent not active /agent health-check not successful. It set l3_agent as "unknown" But when l3_agent active agent like
process force-stop/crash scenarios . When the agent is recovered the l3_agent state not reverted back to original state .
When some update happens on the router , it able to restore the actual state but not after agent is restored / recovered
description: | updated |
Changed in neutron: | |
assignee: | nobody → Mohankumar (mohankumar-n) |
Changed in neutron: | |
status: | New → Incomplete |
description: | updated |
description: | updated |
Changed in neutron: | |
status: | Incomplete → New |
status: | New → Incomplete |
Hi,
Thank you for the report! It sounds like there's a bug here, but could you please give us a bit more detail on how to reproduce this, like exact commands that lead to the error?