ovs is dead but ovs agent is up
Bug #1910946 reported by
norman shen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
norman shen |
Bug Description
we are using openstack-neutron rocky with openvswitch versioned 2.10.0
We are using ubuntu 18.04 which shipped with a libc6 bug, reported here https:/
My question is that when this bug happens ovs agent will not working and reported dead observed from log,
but it still reports hearthbeat to neutron-server which is problematic because users will be unaware that ovs-agent is working anymore but looking at agent service state.
Changed in neutron: | |
assignee: | nobody → norman shen (jshen28) |
To post a comment you must log in.
Are you suggesting that the agent should report itself dead when the ovs deadlock occurs?
1) How would the agent determine OVS is deadlocked? /github. com/openvswitch /ovs-issues/ issues/ 175 and just move on?
2) Isn't it easier to adopt the workaround indicated in https:/