)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"90b359335f59aa4711793d71fd2e9630f30b4a0f","unresolved":true,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This problem is only in Ussuri but not in Victoria release and further"},{"line_number":19,"context_line":"as device_owner is changed to network:distributed for dhcp ports [1]"},{"line_number":20,"context_line":"and dhcp_server update is handled in [2]"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Closes-Bug: #1950180"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"a45eb07c_bf92b0de","line":20,"updated":"2022-01-04 03:31:41.000000000","message":"is non-OVN settings will be affected ?\nthis V+ release note affect is OVN only?","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"},{"author":{"_account_id":10366,"name":"Hemanth N","email":"hemanth.nakkina@canonical.com","username":"Hemanth"},"change_message_id":"383e9c2fd109570bb3b32e20f0c7f5998ee23248","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This problem is only in Ussuri but not in Victoria release and further"},{"line_number":19,"context_line":"as device_owner is changed to network:distributed for dhcp ports [1]"},{"line_number":20,"context_line":"and dhcp_server update is handled in [2]"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Closes-Bug: #1950180"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"628f0d7a_918c9617","line":20,"in_reply_to":"463bd538_72845634","updated":"2022-01-30 01:07:28.000000000","message":"Done","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"},{"author":{"_account_id":10366,"name":"Hemanth N","email":"hemanth.nakkina@canonical.com","username":"Hemanth"},"change_message_id":"71d4faabb5eb679eadee282b6618adaeb6bbf9d4","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This problem is only in Ussuri but not in Victoria release and further"},{"line_number":19,"context_line":"as device_owner is changed to network:distributed for dhcp ports [1]"},{"line_number":20,"context_line":"and dhcp_server update is handled in [2]"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Closes-Bug: #1950180"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9412bfe7_9b77f4a0","line":20,"in_reply_to":"628f0d7a_918c9617","updated":"2022-03-17 10:49:27.000000000","message":"Hi jichenjc,\n\nI am wrong in my earlier statement, the problem is observed in OVN based cloud in Ussuri with neutron 16.4.1 and fixed in 16.4.2. And non-OVN based cloud does not have this issue. Please see https://bugs.launchpad.net/nova/+bug/1950180/comments/4 for more information. I am going to abandon this patch.","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"},{"author":{"_account_id":10366,"name":"Hemanth N","email":"hemanth.nakkina@canonical.com","username":"Hemanth"},"change_message_id":"45527dbce88bc400b6e3da6c445f4879ba95f94c","unresolved":true,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This problem is only in Ussuri but not in Victoria release and further"},{"line_number":19,"context_line":"as device_owner is changed to network:distributed for dhcp ports [1]"},{"line_number":20,"context_line":"and dhcp_server update is handled in [2]"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Closes-Bug: #1950180"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"463bd538_72845634","line":20,"in_reply_to":"a45eb07c_bf92b0de","updated":"2022-01-05 07:24:53.000000000","message":"Both OVN and non-OVN will be affected in Ussuri without this fix.\nSame goes with V+, both OVN/non-OVN works fine from V release.","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":19234,"name":"Alexey Stupnikov","email":"aleksey.stupnikov@gmail.com","username":"astupnikov"},"change_message_id":"36faa2daed1d8b26c5de46722c1827b5c6f458d6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"57f9f6ad_e5a816f8","updated":"2022-01-31 15:06:42.000000000","message":"IMO this change makes sense on a high level: what\u0027s the point of obtaining DHCP server\u0027s IP addresses if DHCP is disabled for some subnet? At the same time, for loop contains a number of dhcp-related calculations which should be skipped if enable_dhcp is false: for example, what\u0027s the point in requesting information about ports which wouldn\u0027t be used later? IMO an extra if condition would make sense here + we need to tune existing if statement validating enable_dhcp flag for subnet.","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"},{"author":{"_account_id":10366,"name":"Hemanth N","email":"hemanth.nakkina@canonical.com","username":"Hemanth"},"change_message_id":"71d4faabb5eb679eadee282b6618adaeb6bbf9d4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a5258c77_115fa12e","in_reply_to":"57f9f6ad_e5a816f8","updated":"2022-03-17 10:49:27.000000000","message":"Yes, thats a better way to avoid unnecessary calculations. However this problem is now fixed in neutron side without any changes in Nova and I am going to abandon this patch. However your suggestion is still applicable outside the scope of this bug.","commit_id":"f70c71bc07bd89f7abd6011d4bacd80d3ea483df"}]}