)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"28197cc2c9b91a75c7ca60435f81d511b783537b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"14fa941e_f7c948af","updated":"2026-09-07 15:03:03.000000000","message":"Shit, https://review.opendev.org/c/openstack/nova/+/848886 was actually the change that made it possible to trigger evacuation while another evacuation was running, by removing the task_state guard. That is was too wide of a change. It no just allowed starting an evacuation from some task_states but allowed to start one from rebuilding, which is could signal an ongoing evacuation. And as we see two parallel evacuation should not be executed on the same instance. But also it shows that there is an intention to allow triggering evacuation for a VM that has not finished action on it. Of course if that action cannot move forward as the compute it is triggered on is dead then the evac make sense, but if the action is actually in progress then we still cannot allow an evac to start as the two active action will overwrite each other changes in the DB.","commit_id":"83850e493d18d0a0353249762214291d2a8bbe95"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"4ff40f98d77889aff676b0e85062b40b83761544","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b09532e7_b4a95ccf","updated":"2026-11-06 16:12:33.000000000","message":"need work based on the PTG discussion","commit_id":"68a1742c46c812df1c40b82b7068cd9e0f209729"}]}