)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"d9ed5d744fbccc516e9c7eadec67576a48ad0051","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"1103bcd2_dc83a5ba","updated":"2025-05-30 14:26:09.000000000","message":"Open question. If we implement this, the final result of the backup node will be actually disabled but running the virtual machines which were in the host maintenance.\n\nHaving instances running in a disabled node sounds a bit weird to me, is that an expected situation from an operational point of view?, What a cloud admin would expect in that case?, adding a parameter to enable/disable this behavior (restore of previous compute state) would be too much?\n\nNote this is changing the behavior of the strategy so at least it should be documented.","commit_id":"9c1b51d612d77d94ac3af1ee2e3fcae54612e14d"}]}
