You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of our libovsdb ops delete rows that would otherwise be garbage collected by the real OVSDB server.
One of the main reasons we do that is because our test server does not have support for garbage collection. So our code either does delete ops that wouldn't be strictly necessary, which requires for us to be extra careful to not incur in referential integrity violations that could happen if we deleted rows that are still referenced from other places; or if we don't do those delete ops, to account for the leftover rows in the tests potentially hiding other issues.
There is ongoing effort to add referential integrity support in the test server: ovn-org/libovsdb#375
When that is done, we need to:
bump libovsdb, fixing our tests of referential integrity violations and cleaning up all leftovers that will now be garbage collected
go through our delete ops and remove those that are covered by garbage collection
The text was updated successfully, but these errors were encountered:
Many of our libovsdb ops delete rows that would otherwise be garbage collected by the real OVSDB server.
One of the main reasons we do that is because our test server does not have support for garbage collection. So our code either does delete ops that wouldn't be strictly necessary, which requires for us to be extra careful to not incur in referential integrity violations that could happen if we deleted rows that are still referenced from other places; or if we don't do those delete ops, to account for the leftover rows in the tests potentially hiding other issues.
There is ongoing effort to add referential integrity support in the test server: ovn-org/libovsdb#375
When that is done, we need to:
The text was updated successfully, but these errors were encountered: