)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"d9c8142ce6e614760e379cda342c3e8c069c1a98","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"eb341d29_4f6fbc18","updated":"2025-03-24 13:21:06.000000000","message":"validating","commit_id":"e1541f10fc3b0e30d2f2b5a4fe777cb9724e7c23"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"d794def0b577e9df7cba6f7cb2ace78fe7d34466","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"0d50bb0d_4ae66074","updated":"2025-04-10 14:46:45.000000000","message":"As discussed in PTG, let\u0027s unblock this and have this backported till stable/2024.2","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"d0b6939c6e739aabe20d368c69210d5aed0fd352","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"106f4fb5_0be0553d","updated":"2025-04-01 11:21:14.000000000","message":"definetly we should use threadpool, single thread significantly impact performance, similar was reported here https://review.opendev.org/c/openstack/neutron/+/938406","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"47d0cd0f9e999d1c54a861ca5b19be1c0878f2a6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9319f780_5015d631","updated":"2025-04-01 11:08:49.000000000","message":"shall we discuss this one during the meeting?","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"0043c9452dc5c48cf8a14564c53a1f5a74e10aff","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9da706a9_f88346ae","in_reply_to":"106f4fb5_0be0553d","updated":"2025-04-02 07:49:38.000000000","message":"Please, read the bug first: https://bugs.launchpad.net/neutron/+bug/2070376. In the DHCP agent, there is no performance impact on limiting the pool to 1.\n\nThis is a testing patch, in order to validate what is causing the problem in the DHCP. Most probably is https://review.opendev.org/c/openstack/neutron/+/945315","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"3c99b9f8a1b4d07929dc7b566df8ad0492149bc6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9e53c14d_749710f2","in_reply_to":"3d831948_60c77d0f","updated":"2025-04-02 12:29:43.000000000","message":"wow its very interesting, provisioning blocks should not allow to start VM unless DHCP is completed for VM port. Which means that either provisioning blocks does not work or this change somehow affects dhcp (for example it triggers dnsmasq restart later when handle other port (non VM port) from same network and it takes affect on the dhcp for VM).","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"0949d14d9ea1920ac1562cb8a11a603875b0ed99","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"50f3d09d_e4f6aa28","in_reply_to":"4edb9cbf_cc522e52","updated":"2025-04-07 10:07:57.000000000","message":"@ralonsoh@redhat.com it\u0027s the same i linked above i.e https://review.opendev.org/c/openstack/neutron/+/945433.\nCurrently had removed depends-on, but same patch was used for testing no revert, single revert and both revert and above is the summary of the results.","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":13861,"name":"yatin","email":"ykarel@redhat.com","username":"yatinkarel"},"change_message_id":"345c6d0fac2ed5f5ecbe504469bf3f60c848ae7f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"3d831948_60c77d0f","in_reply_to":"8e867d2f_a3b8569d","updated":"2025-04-02 08:34:15.000000000","message":"To summarize test patch results from https://review.opendev.org/c/openstack/neutron/+/945433, not seen a single failure in 250+ runs with this patch.\n\nWhile with https://review.opendev.org/c/openstack/neutron/+/945315 or no reverts seen a few failures 4-5 in 140+ runs","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"689db47732fdef921e06bd657f073529bfe60289","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8e867d2f_a3b8569d","in_reply_to":"9da706a9_f88346ae","updated":"2025-04-02 08:24:53.000000000","message":"I think its more complicated than how its described in the bug. Even when we have 1 process and use multiple green threads (when each tread handles own port or network). The impact when single resource handling takes longer time (compare to others) will not block other resources handled in greentreads, but when we limit it to 1, unless `slow` port/network handling is completed we will even not start handling other resources.\n\nI\u0027ve check https://bugs.launchpad.net/neutron/+bug/2101840 the sympthom is that VM is not getting DHCP, but we have privisioning blocks, and it does not matter how long it takes to setup DHCP for port, VM should not be started. So the bug attached indeed seems can\u0027t be fixed by just performance issue.","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"7c32f0992f6e396c5536efabce8d1538acd8a40c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4edb9cbf_cc522e52","in_reply_to":"9e53c14d_749710f2","updated":"2025-04-07 10:00:10.000000000","message":"Hi Yatin, what is the testing patch for this revert?","commit_id":"a5243334cb7ac31f3ab7760425305726a4f75113"}]}