Comment 11 for bug 1605089

It seems like we should be able to turn this into a failure-rollback scenario, as well. If we're updating a resource, we know the old and new values from the Neutron DB point of view. We can use ovsdb verify() calls to ensure that the old values we expect are still there in the OVN database for an update to be successful. Does that make sense?