)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"2cb53d9c18e834f1d30280fdce450fbd0935878b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"bb9e4e91_2cea4430","updated":"2026-07-20 09:49:39.000000000","message":"I\u0027m not ok with this change that breaks the assumption of having a resource revision per Neutron resource, directly dependent on the Neutron resource, not a parent. This implementation will require a explicit `delete_revision`.\n\nInstead, having a `bump_revision(context, segment, TYPE_SEGMENTS)` each time we modify the parent resource will keep this 1:1 assignation untouched.","commit_id":"e78c8b51c82bb1293fc612f77fbc60a80762a52b"},{"author":{"_account_id":4694,"name":"Miguel Lavalle","email":"miguel@mlavalle.com","username":"minsel"},"change_message_id":"cedb12a545ac0eb0f7c5bb0c51f9a33a0efc06c4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"20e7929d_3a8ea571","updated":"2026-07-09 14:27:42.000000000","message":"recheck failure in neutron-ovs-tempest-dvr-ha-multinode-full unrelated to change","commit_id":"e78c8b51c82bb1293fc612f77fbc60a80762a52b"},{"author":{"_account_id":4694,"name":"Miguel Lavalle","email":"miguel@mlavalle.com","username":"minsel"},"change_message_id":"1368d32abb1294c979e010ee10627e83dc1622bb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"3015377c_afe7a40f","updated":"2026-07-08 14:39:38.000000000","message":"recheck. Funcitonal tests and grenade job failures related to installation issues","commit_id":"e78c8b51c82bb1293fc612f77fbc60a80762a52b"}],"neutron/db/ovn_revision_numbers_db.py":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"2cb53d9c18e834f1d30280fdce450fbd0935878b","unresolved":true,"context_lines":[{"line_number":180,"context_line":""},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"@db_api.retry_if_session_inactive()"},{"line_number":183,"context_line":"def bump_revision(context, resource, resource_type, dependent_resource\u003dNone,"},{"line_number":184,"context_line":"                  dependent_resource_type\u003dNone):"},{"line_number":185,"context_line":"    revision_number \u003d ovn_utils.get_revision_number(resource, resource_type)"},{"line_number":186,"context_line":""}],"source_content_type":"text/x-python","patch_set":3,"id":"0d542367_421e5cf6","line":183,"range":{"start_line":183,"start_character":4,"end_line":183,"end_character":17},"updated":"2026-07-20 09:49:39.000000000","message":"After reviewing the upper patches, this approach breaks the assumption of the OVN resource deletion when the FK is set to null. In this case, the FK is not the resource itself (segments) but the network.\n\nI would suggest to make `segments` a resource to be monitored by OVN at the same level as the others. That will require to explicitly add a segment bump for each network operation. For example:\n```\ndef update_network(self, context, network, ...):\n    segments \u003d get_network_segments(context, network[\u0027id\u0027])\n    # ... update each segment LS in OVN ...\n    for segment in segments:\n        # Bump segment standardattr so maintenance can detect failures\n        segment_obj \u003d NetworkSegment.get_object(context, id\u003dsegment[\u0027id\u0027])\n        segment_obj.bump_revision()\n        db_rev.bump_revision(context, segment, TYPE_SEGMENTS)\n```","commit_id":"e78c8b51c82bb1293fc612f77fbc60a80762a52b"}]}