evacuation, running VM shown stop after compute service started at firsh host.

[Amit Uniyal]

Description
===========
After evacuation, when original host/node become seriveable (like nova is running properly in host ), VM status changed in nova DB as 'SHUTOFF' automatically from 'ACTIVE'.

This is because on nova initialization nova checks for all evacuated instances on original server-host, and delete local copy from host. and also update status at DB.

Steps to reproduce (reporduced 100%)
====================================

- create a VM (you must have multinode setup to run evacuation)
- get server-host
    openstack server list --long

- server-host - stop service
    systemctl stop devstack@n-cpu

- server-host - force-down compute service
    openstack compute service --down <host> vm1

- stop VM
    openstack server stop vm

- look for VM power state - stuck at powering off
    openstack server list --long

- open logs api/cpu in both nodes
- evacuate VM
     openstack server evacuate --host=<target-host> --os-compute-api-version 2.29

- server moved to new host and become active

- orginal server-host start compute service (systemctl)

- look for VM status
    openstack server list --long

Expected result
===============
After service start at original host, it should not affect VM in any way.

Actual result
=============
openstack server list shows -

VM status went shutoff, task state=None, power=no state (eventually goes to Shutdown),
VM stays at expected new host

although VM can be used, can login to server (tried with virsh)

Environment
===========

Nova: current master or future 2024.2

[Amit Uniyal (auniyal)]

service restart in original host logs attached

server-id: 3a8b9820-018e-4ad6-a59c-7d99b5eaf74c