Description of problem:
Due to a refactor PR to try to clean up some of the libovsdb interaction code in ovn-kube, the behavior of updating columns in the database back to their default values was changed. Previously the code would specify which columns/fields of a row that need to be updated. With the PR, now it is assumed that only fields with non-default values need to be updated:
The consequence of this is that for certain column types (map, slice, pointer) the values will never get updated if they are set back to their default value. For example, if there is a logical switch port who currently has a vlan tag of 5, and the port is updated to remove the tag, this update will never happen because of this bug. Additionally if there is a column that holds a slice or map type, and it is trying to be set back to empty that will never happen. Since this refactor touched many places in ovnk, this regression is likely across multiple features and functionality.
*** Bug 2094903 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days