)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9236,"name":"Jon Bernard","email":"jobernar@redhat.com","username":"jbernard"},"change_message_id":"303cb32bb8c6a04e3f40b38beaf986a2a95ac459","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0fc5cb05_c9273f77","updated":"2026-06-27 15:00:24.000000000","message":"Note, if you look at the threading tests (https://83ed79f1981651d9d8d4-66ce5f117c645ca152390f12473225b2.ssl.cf1.rackcdn.com/openstack/4b93c3b35f7c4d98a1203312cf26ac1d/testr_results.html) the 2 backup tests that were failing are now passing on both eventlet and non-eventlet.  Whatever we end up going with, that\u0027s something to look for.","commit_id":"534e347a765a4161fcc41f6cbe9575157c3a3bfb"},{"author":{"_account_id":9236,"name":"Jon Bernard","email":"jobernar@redhat.com","username":"jbernard"},"change_message_id":"f97f05f75c785521e65d5df98e9c6f35b22855b8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dfc883f2_6759e7dc","updated":"2026-06-26 20:09:15.000000000","message":"There are 1 or 2 other patches that address the same issue, may the cleanest solution win.","commit_id":"534e347a765a4161fcc41f6cbe9575157c3a3bfb"},{"author":{"_account_id":36171,"name":"jayaanand borra","display_name":"jayaanand borra","email":"jayaanand.borra@netapp.com","username":"jayaanan","status":"netapp"},"change_message_id":"53b867e7b498faf40db920b2b6f6c85fbec62093","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e7f294e4_fa7ee8d1","updated":"2026-07-01 09:51:29.000000000","message":"This patch fixes an important cinder-backup startup crash under the native threading backend and may also change the semantics of backup_native_threads_pool_size depending on how the tpool.Proxy() sizing issue is resolved.\n\nRelease note is required for upgrade impact, changed behavior, and important bug fixes. This patch qualifies at least as an important issue fix, and potentially as an upgrade/behavior note as well.","commit_id":"534e347a765a4161fcc41f6cbe9575157c3a3bfb"},{"author":{"_account_id":34860,"name":"Amit Uniyal","email":"auniyal@redhat.com","username":"auniyal"},"change_message_id":"8a8b12a62b9d4b96a65fa35aa70bcb3833f36dda","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0f82138f_5e149167","in_reply_to":"e7f294e4_fa7ee8d1","updated":"2026-07-03 09:45:01.000000000","message":"yeah good point, but I also wonder this is a part of the broader eventlet-removal, do we really need to inform/warn operators for individual service fixes.\n\nWe might want to have one detailed note when threading backend is fully supported.\nthis is a mosly implementaion detail, not operator facing change like driver specific.\n\nso overall, would any operator change anything in their deployemnt, because of this individual patch, either they will be using theading or eventlet.","commit_id":"534e347a765a4161fcc41f6cbe9575157c3a3bfb"},{"author":{"_account_id":34860,"name":"Amit Uniyal","email":"auniyal@redhat.com","username":"auniyal"},"change_message_id":"8a8b12a62b9d4b96a65fa35aa70bcb3833f36dda","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6c0fe0a6_c687e29d","updated":"2026-07-03 09:45:01.000000000","message":"unit tests are passing and tempest threading job test passed so good, it timeout but its unrelated.\n\nthough its kind wired to me why all passed wit this change, because this is a only top level (service startup) change and driver realted change are pending, so may be we dont have enough tempest coverage, even with https://review.opendev.org/c/openstack/cinder/+/977851 not all test passed\n\noverall looks good to me.","commit_id":"38a4b9877b2cb14a8b051e0d647a70dce046c462"}]}