after restart of a ovn-controller the agent is still down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Felix Huettner |
Bug Description
Assume a neutron setup with the ml2 ovn plugin.
Further assume for the duration of this issue that no changes are made on the user api, so that nb_cfg at the start of the issue is equal to nb_cfg at the end of the issue:
1. Take any ovn-controller that you have and run a openstack network agent show on it; this should say "up" and a valid "heartbeat_
2. Restart the ovn-controller
3. the openstack output should not say down with the unix 0 timestamp as heartbeat
4. Do any change that causes nb_cfg to increase
5. the agent is now up with a proper timestamp
Issue is caused by https:/
in step 2 the southbound database will emit two events:
1. when the ovn-controller first starts, one with the addition of Chassis_Private where nb_cfg and nb_cfg_timestamp is 0
2. when the ovn-controller has finished syncing with the nb_cfg as in SB_GLOBAL and nb_cfg_timestamp with the current timestamp
however the second event is currently filtered by the `match_fn` as `old.nb_cfg` is `0` at this point. In the condition `0` is evaluated to `False` thereby ignoring the event.
This issue might be the same as https:/
Changed in neutron: | |
assignee: | nobody → Felix Huettner (felix.huettner) |
tags: | added: ovn |
Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/865697
Review: https:/