)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"0a3b862ede173dda52f30018497d64531e394c73","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dbe08522_d60edaf3","updated":"2026-01-23 07:50:03.000000000","message":"interesting solution. lets fix the CI","commit_id":"e948492b8d9ffc56c18ecfd04e9e4dc6a318e45c"},{"author":{"_account_id":37230,"name":"Scott Storck","display_name":"Scott S","email":"scott.storck@comless.de","username":"scottstorck","status":"COMPUTERS \u0026 LESSONS GmbH"},"change_message_id":"ac7cbf869360d74c86190e0f02eb2702a2d721ec","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"83013cb1_45aea658","in_reply_to":"dbe08522_d60edaf3","updated":"2026-02-20 04:00:27.000000000","message":"It wasn\u0027t a CI problem, it was the \"wrong\" patch. Patch set 5 works for me tested against master, 2025.1, and 2025.2.","commit_id":"e948492b8d9ffc56c18ecfd04e9e4dc6a318e45c"},{"author":{"_account_id":37230,"name":"Scott Storck","display_name":"Scott S","email":"scott.storck@comless.de","username":"scottstorck","status":"COMPUTERS \u0026 LESSONS GmbH"},"change_message_id":"c84f96f5c4e71b8aa5b454f54fb25da57998dab0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"37977684_a38b1b9e","updated":"2026-02-20 02:09:15.000000000","message":"I fixed the patch set so it works with the master when I test it locally. What else needs to be done? Should I add a file for a release note?","commit_id":"9a7acc11afb8d5ea98b26708764df268197c94af"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"0df9f8ac9a1be6b5504cb6e8ba4d5fb14e6f47b0","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"53deed6c_b33eb1d6","updated":"2026-02-20 08:45:44.000000000","message":"Needs a reno at least, I’m unsure if that can be backported…","commit_id":"9a7acc11afb8d5ea98b26708764df268197c94af"},{"author":{"_account_id":37230,"name":"Scott Storck","display_name":"Scott S","email":"scott.storck@comless.de","username":"scottstorck","status":"COMPUTERS \u0026 LESSONS GmbH"},"change_message_id":"ac7cbf869360d74c86190e0f02eb2702a2d721ec","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ecff9e5c_22119d92","updated":"2026-02-20 04:00:27.000000000","message":"This fixes the bug for me and works without problems on new deployments.\n\nWhen this change gets deployed as part of an update / upgrade, it will cause live migrations to fail, if you update compute nodes in batches using --limit and the source and destination nodes have not both been updated already.\nIn this case the live migration fails with libvirt authentication failed, which is not surprising.\n\nI would think this change will need a release note, as this could cause operators unexpected problems.\n\nPlease let me know what you think.","commit_id":"9a7acc11afb8d5ea98b26708764df268197c94af"}]}