)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"20cdb43fd0758b72c25730568e5a909adb83490b","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8c257de8_39d50cbe","updated":"2025-09-15 09:23:03.000000000","message":"@winterma.dong@gmail.com Hello, please add release note.","commit_id":"308934aaa3481a116dde8876032d4346dfa787aa"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"37d12f15d5eec6376ae5b5c8dffde6363f0fa105","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cff3caa1_c1ec1c3d","in_reply_to":"8c257de8_39d50cbe","updated":"2025-09-15 11:03:25.000000000","message":"Done","commit_id":"308934aaa3481a116dde8876032d4346dfa787aa"},{"author":{"_account_id":9725,"name":"Dong Ma","email":"winterma.dong@gmail.com","username":"larainema"},"change_message_id":"d4187d3126111df83cfba3bfaa0374c2771ea251","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ac2c6885_62323e91","updated":"2025-11-07 16:26:57.000000000","message":"@jjasek@redhat.com @t.v.ovtchinnikova@gmail.com @openstack@dopieralski.pl @dcu995@gmail.com can you help review this? thanks","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"2797c435e9c2eb517cfbc10172f57d1dfd434813","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4e905df9_1366d060","updated":"2025-10-14 00:53:40.000000000","message":"Folks, we\u0027ve pushed this nearly a month ago.. can we get some eyes?","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":35133,"name":"Jan Jasek","email":"jjasek@redhat.com","username":"janjasek"},"change_message_id":"f1919817b15c4a03e6232844a598ad810a67d58b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"15e442d2_f4d054b7","updated":"2025-11-12 23:43:41.000000000","message":"Hello @winterma.dong@gmail.com, first of all… I am super sorry for it taking sooo long… I was really busy the last few weeks and to verify this patch was much more complicated than I expected (starting with that it requires a multi-node environment, and ending with that the bug description missing a few very important parts or the parts are not there highlighted enough and I am not super familiar with nova so it were blind points for me).\n\nAnyway… I was finally able to verify it and from my practical verification your patch seems to be working well.\n\nSo it is +2 from me and thank you for your patience!","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":35133,"name":"Jan Jasek","email":"jjasek@redhat.com","username":"janjasek"},"change_message_id":"0ff5a5f9ba54020271f1b968a0168fc4dcfc62d1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"5edb7dcd_89839fba","updated":"2025-10-17 17:27:19.000000000","message":"Hi guys, Sorry for waiting too long, I was really busy and also I do not have a multi-node test environment deployed by default.\nAnyway, I deployed a new devstack multi-node test environment because I wanted to try to reproduce the issue from the bug report and practically verify the fix but I can not reproduce it.\n\nI have two nodes:\nfirst one - controller+compute node\nsecond one - only compute node.\nI have a cirros image with the property os_distro\u003d\u0027cirros\u0027.\nI have 2 host aggregates:\nag_cirros with property os_distro\u003d\u0027cirros\u0027 and host jjasek-multi-controller-node and\nag_fedora with property os_distro\u003d\u0027fedora\u0027 and host jjasek-multi-compute-node.\n\nIn point 5 is “Create an instance named \u0027vm1\u0027 from cirros image. The instance is scheduled to osp10-comp02 by AggregateImagePropertiesIsolation.” \nBy my naming, it should be scheduled to jjasek-multi-controller-node (which is host for ag_cirros with property os_dristro\u003d’cirros’) If I am right.\nBut for me it creates “vm1” once on the computer node, next time on the controller node. Based on the Bug report I expect it should be scheduled on the host that is connected to ag_cirros with property os_dristro\u003d’cirros’?\n\nAlso when I try to do in CLI: nova live-migration b741c474-c32f-4e58-9f9e-b9c5d6c8b1d5. It works without any struggles/errors and migrates the VM to another host.\nWhen I try to do it in Horizon: I can see Status ‘Migrating’ and Task ‘Migrating’ and the VM is migrated to another host without any error too.\n\nIt works completely the same for me with the patch applied and also without the patch applied.\n\nI can see the bug report (so the steps too) are almost 7 years old.\nCan any of you verify that the steps in the bug report are still relevant? Or can you try to reproduce it in your environment?\nAs I am working mainly around Horizon, I very rarely work with multi-node devstack and the same for debugging nova functions. So it is highly possible I am doing something wrong, I set something incorrectly or the steps in the bug report are not complete (sufficiently detailed).\nFortunately I can see a lot of people active around this patch pinging so I believe someone will be able to clarify it for me and try to verify in your environments.\n\nThank you!","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":6914,"name":"Tatiana Ovchinnikova","email":"t.v.ovtchinnikova@gmail.com","username":"tmazur"},"change_message_id":"8ad21577af7e342389f98aa5c9826301b56fc7a2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"121ff8bf_2164f575","updated":"2025-12-18 19:37:49.000000000","message":"LGTM, thank you!","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":9725,"name":"Dong Ma","email":"winterma.dong@gmail.com","username":"larainema"},"change_message_id":"ce532418e120e96fe3a06c4e5a43f796957a3555","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e6ee7163_2eefa7b4","in_reply_to":"15e442d2_f4d054b7","updated":"2025-11-13 15:11:34.000000000","message":"Thanks @jjasek@redhat.com for helping review","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":9725,"name":"Dong Ma","email":"winterma.dong@gmail.com","username":"larainema"},"change_message_id":"18ad7e5aab07ea1dd31d11f0e5917b7e6108e503","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b5bc9df7_c79e8665","in_reply_to":"5edb7dcd_89839fba","updated":"2025-10-17 23:22:38.000000000","message":"Hi Jan,\n\nThe live migration without specify the destination host all works as expected, but the live migration with the destination host the horizon have different behavior with cli as didn\u0027t specify the microversion. Prior to microversion 2.30, specifying a host will bypass validation by the scheduler.\n\nhttps://docs.openstack.org/api-ref/compute/#live-migrate-server-os-migratelive-action","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":35133,"name":"Jan Jasek","email":"jjasek@redhat.com","username":"janjasek"},"change_message_id":"5eac3f6c100f5684bc6215208f03a6896786d0f9","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f0f28a89_39303c59","in_reply_to":"b5bc9df7_c79e8665","updated":"2025-10-22 11:23:06.000000000","message":"Hello @winterma.dong@gmail.com,\nI am little confused that there in the api-ref is mentioned that \n“Prior to microversion 2.30, specifying a host will bypass validation by the scheduler”\n\nWhen I try to use --os-compute-api-version 2.2 then:\nstack@jjasek-multi-controller-node:~/horizon$ openstack --os-compute-api-version 2.2 server migrate --live-migration --host jjasek-multi-compute-node b741c474-c32f-4e58-9f9e-b9c5d6c8b1d5\n--os-compute-api-version 2.30 or greater is required when using --host\n\nWhat am I doing wrong? Is there anything else that needs to be set? Or am I completely missing something (logically)?","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"},{"author":{"_account_id":9725,"name":"Dong Ma","email":"winterma.dong@gmail.com","username":"larainema"},"change_message_id":"1e3c48bf9cacd7581ad043cd3d62624726b7422a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d23362b8_bc8e15c8","in_reply_to":"f0f28a89_39303c59","updated":"2025-10-22 13:09:24.000000000","message":"Hi @jjasek@redhat.com,\n\nI think the api-ref doc means:\n\nBefore 2.30: if you somehow used the host field directly via the REST API (not the CLI), Nova would bypass scheduler validation.\n\nFrom 2.30 onward: host was officially added as a valid parameter, and validation logic changed to use the scheduler.\n\n\nAnd the python-openstackclient enforces that rule — if you try to use --host with a microversion lower than 2.30, it refuses the command.","commit_id":"60455e5ffe5129a592f35672656ab4c2ad1b87f9"}]}