As the openstack have upgraded to train version in stx3.0, there are some changes in cold migrate process, that the VM state will be rollback after migrate failed.
2020-05-08 04:22:44.343 755021 INFO nova.compute.manager [req-5f2e3ec2-9ced-41b2-a5be-9fd4180dcc3d e30d8a9ccb254aad88ef83b1c22aa5cf cfb538569c2346d2971f9a8b49ba405c - default default] [instance: 891a95dc-1a76-403a-a912-c360c2a85548] Setting instance back to active after: Instance rollback performed due to: Unable to migrate instance (891a95dc-1a76-403a-a912-c360c2a85548) to current host (controller-0).
As the openstack have upgraded to train version in stx3.0, there are some changes in cold migrate process, that the VM state will be rollback after migrate failed.
2020-05-08 04:22:44.343 755021 INFO nova.compute. manager [req-5f2e3ec2- 9ced-41b2- a5be-9fd4180dcc 3d e30d8a9ccb254aa d88ef83b1c22aa5 cf cfb538569c2346d 2971f9a8b49ba40 5c - default default] [instance: 891a95dc- 1a76-403a- a912-c360c2a855 48] Setting instance back to active after: Instance rollback performed due to: Unable to migrate instance (891a95dc- 1a76-403a- a912-c360c2a855 48) to current host (controller-0).
So I think the active state is't a bug