)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"dcaa95a955b15881d7c8128902423546d8e998fe","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Handle no more IP addresses available during a network sync"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In some corner cases, like when sb_sync is performed after OVS to OVN"},{"line_number":10,"context_line":"migration, an implicit metadata port creation on a network with"},{"line_number":11,"context_line":"depleted IP pool can raise IP allocation error. Just catch and log"},{"line_number":12,"context_line":"this error such that the db_sync tool can finish syncing."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1e4856dc_bed513df","line":9,"range":{"start_line":9,"start_character":32,"end_line":9,"end_character":39},"updated":"2023-04-18 19:37:22.000000000","message":"nit: typo","commit_id":"7b67d4152e5f091f2f51500cfae80884884faae8"},{"author":{"_account_id":34271,"name":"Miro Tomaska","display_name":"Miro Tomaska","email":"mtomaska@redhat.com","username":"mtomaska"},"change_message_id":"1679f6a56595688f1f92cee8df9bebce919ec1c7","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Handle no more IP addresses available during a network sync"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In some corner cases, like when sb_sync is performed after OVS to OVN"},{"line_number":10,"context_line":"migration, an implicit metadata port creation on a network with"},{"line_number":11,"context_line":"depleted IP pool can raise IP allocation error. Just catch and log"},{"line_number":12,"context_line":"this error such that the db_sync tool can finish syncing."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"f89422be_2ae66aea","line":9,"range":{"start_line":9,"start_character":32,"end_line":9,"end_character":39},"in_reply_to":"1e4856dc_bed513df","updated":"2023-05-16 21:34:00.000000000","message":"Done","commit_id":"7b67d4152e5f091f2f51500cfae80884884faae8"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"dcaa95a955b15881d7c8128902423546d8e998fe","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c4a6848f_ca2f5ef9","updated":"2023-04-18 19:37:22.000000000","message":"Thanks for the patch. I was wondering if we should run the db-sync again after the cleanup phase. For external networks it might not be useful as they don\u0027t use DHCP but internal networks have a DHCP port per agent and cleanup deletes those. That should free up some IPs from the allocation pool.","commit_id":"7b67d4152e5f091f2f51500cfae80884884faae8"}]}