)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"b45b89c3d1ab833096855a71d73f1551c3aa9b0f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a5d1213a_27971d8e","updated":"2026-07-23 20:34:33.000000000","message":"I\u0027d like to have this backported to 2026.1","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"91a9b019d5d3032d51705f1ba2f1e54a2124a4de","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"465bcfa7_dfc0525b","updated":"2026-07-24 14:46:12.000000000","message":"recheck neutron-tempest-plugin-openvswitch","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"bc7ba510a788e267e8ad302d4e4f438157ca1c5e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1b089947_a1a6948e","updated":"2026-07-28 08:26:33.000000000","message":"the test failure test_update_network_segment_range_failed_with_existing_range_impacted seems to be related to the the patch, please check","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"cea0e2bd1bfc6d731e96bc8ed2946a3630d8c782","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"afcb7954_67c6dad0","in_reply_to":"1b089947_a1a6948e","updated":"2026-07-28 08:34:49.000000000","message":"to be more precise I am not fully sure that it is related by the logs.\nI checked also opensearch and by that result this failure is happening only on your patch ( https://opensearch.logs.openstack.org/_dashboards/app/data-explorer/discover/?security_tenant\u003dglobal#?_g\u003d(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30d,to:now))\u0026_a\u003d(discover:(columns:!(build_status,build_change),interval:auto,sort:!()),metadata:(indexPattern:\u002794869730-aea8-11ec-9e6a-83741af3fdcd\u0027,view:discover))\u0026_q\u003d(filters:!(),query:(language:kuery,query:\u0027message:%22line%20141,%20in%20test_update_network_segment_range_failed_with_existing_range_impacted%22\u0027)) ), but I can\u0027t see now what is wrong with this tempest test in this case.","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"c5fcf630b72c85faa3c9934ff3f44c76006a5be5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a10dcf53_b067919a","in_reply_to":"afcb7954_67c6dad0","updated":"2026-08-04 23:56:28.000000000","message":"Yeah the test is literally bad. The test creates a network segment range of 1100 to 1105. It then creates a network and neutron assigns it segment_id\u003d1100. Then we attempt an update of the network segment range to 1100 to 1155 and the test expects that to throw an exception.","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"18ff5756f9cbad098b0c8ddacb131eb885dce61b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"0bd07926_15b40201","updated":"2026-08-10 21:09:33.000000000","message":"Looks good except for \u0027tenant\u0027","commit_id":"d4e08068281a462ef5f26ef4f4ba68d2b68f0b91"}],"releasenotes/notes/fix-network-segment-range-shrink-202881cfd8236605.yaml":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"b743281a11a18a94525e1769967672e77f050776","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixed a bug where a network segment range could not be shrunk to a"},{"line_number":5,"context_line":"    boundary that lands exactly on an allocated segment. The check that"},{"line_number":6,"context_line":"    guards against stranding allocated segments used inclusive comparisons,"},{"line_number":7,"context_line":"    so updating a range whose new minimum or maximum equalled the lowest or"},{"line_number":8,"context_line":"    highest allocated segment was wrongly rejected as still being referenced"},{"line_number":9,"context_line":"    by a tenant network. The update is now allowed as long as every allocated"},{"line_number":10,"context_line":"    segment remains within the new range. See bug"},{"line_number":11,"context_line":"    `2161678 \u003chttps://bugs.launchpad.net/neutron/+bug/2161678\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"4985d847_abd34b35","line":10,"range":{"start_line":4,"start_character":3,"end_line":10,"end_character":49},"updated":"2026-07-24 14:50:21.000000000","message":"This is too long, too implementation focused (that will be read by users) and starts with \"fixed a bug\" in the \"fixes\" section. My proposal:\n```\nShrinking a network segment range to boundaries that coincide with the\nlowest or highest allocated segment was incorrectly rejected with a\n``ConflictException`` claiming the range is still referenced by tenant\nnetworks. The update is now allowed as long as all allocated segments\nremain within the new range boundaries. See bug\n`2161678 \u003chttps://bugs.launchpad.net/neutron/+bug/2161678\u003e`_.\n```","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"c5fcf630b72c85faa3c9934ff3f44c76006a5be5","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixed a bug where a network segment range could not be shrunk to a"},{"line_number":5,"context_line":"    boundary that lands exactly on an allocated segment. The check that"},{"line_number":6,"context_line":"    guards against stranding allocated segments used inclusive comparisons,"},{"line_number":7,"context_line":"    so updating a range whose new minimum or maximum equalled the lowest or"},{"line_number":8,"context_line":"    highest allocated segment was wrongly rejected as still being referenced"},{"line_number":9,"context_line":"    by a tenant network. The update is now allowed as long as every allocated"},{"line_number":10,"context_line":"    segment remains within the new range. See bug"},{"line_number":11,"context_line":"    `2161678 \u003chttps://bugs.launchpad.net/neutron/+bug/2161678\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"a9cfaa38_77284a07","line":10,"range":{"start_line":4,"start_character":3,"end_line":10,"end_character":49},"in_reply_to":"4985d847_abd34b35","updated":"2026-08-04 23:56:28.000000000","message":"Done","commit_id":"45c3a6963ad04f13ee58528d77ff9e62678b299d"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"18ff5756f9cbad098b0c8ddacb131eb885dce61b","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Shrinking a network segment range to boundaries that coincide with the"},{"line_number":5,"context_line":"    lowest or highest allocated segment was incorrectly rejected with a"},{"line_number":6,"context_line":"    ``ConflictException`` claiming the range is still referenced by tenant"},{"line_number":7,"context_line":"    networks. The update is now allowed as long as all allocated segments"},{"line_number":8,"context_line":"    remain within the new range boundaries. See bug"},{"line_number":9,"context_line":"    `2161678 \u003chttps://bugs.launchpad.net/neutron/+bug/2161678\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"61174cb6_4649bc71","line":6,"range":{"start_line":6,"start_character":68,"end_line":6,"end_character":74},"updated":"2026-08-10 21:09:33.000000000","message":"s/project\n\nSorry, i\u0027ve been changing all the code and docs to remove \u0027tenant\u0027.","commit_id":"d4e08068281a462ef5f26ef4f4ba68d2b68f0b91"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"a6113f272a49e82f97767e8fec6e0f5ae4a319ad","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Shrinking a network segment range to boundaries that coincide with the"},{"line_number":5,"context_line":"    lowest or highest allocated segment was incorrectly rejected with a"},{"line_number":6,"context_line":"    ``ConflictException`` claiming the range is still referenced by tenant"},{"line_number":7,"context_line":"    networks. The update is now allowed as long as all allocated segments"},{"line_number":8,"context_line":"    remain within the new range boundaries. See bug"},{"line_number":9,"context_line":"    `2161678 \u003chttps://bugs.launchpad.net/neutron/+bug/2161678\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"70b9fadf_b5acb2d3","line":6,"range":{"start_line":6,"start_character":68,"end_line":6,"end_character":74},"in_reply_to":"61174cb6_4649bc71","updated":"2026-08-10 21:22:14.000000000","message":"Done","commit_id":"d4e08068281a462ef5f26ef4f4ba68d2b68f0b91"}]}