Description of problem:
engine-backup --mode=restore imports the engine DB and the required configuration files but it still requires a run of engine-setup to properly align the engine DB to installed version.
So, it enforces the engine service to be down and it asks the user to manually run engine-setup at the end.

If for any reason (for instance because the engine is on a VM and the user forgot to set global maintenance mode: within a few minutes ovirt-ha-agent is going to reboot the engine VM) the system reboots before the user could run engine-setup, the engine service is not disabled and so it restart with a possibly incompatible database resulting in obscure errors.

Ensuring that the engine-service is explicitly disabled and not just stopped will prevent this; enabling again the engine service will be up to engine-setup.

Version-Release number of selected component (if applicable):


How reproducible:
The issue is systematic, the symptoms (possibly none) are instead related to the differences between the system where the backup got generated with the system where it got restored.

Steps to Reproduce:
1. restore an engine backup
2. reboot the system before running engine-setup
3. after the reboot check the status of the engine

Actual results:
the engine was just stopped but not disabled so after a reboot it will restart also if the DB has still to be upgraded

Expected results:
the engine will not restart till the user runs engine-setup again

Additional info:
The user has a valid engine backup so he could simply try again the restore procedure.