Description of problem:

The testing flow described in the following document isn't clear enough and should be more clear about how to handle the hosts and the HE vm before upgrading the host's rpms to 4.0 to perform hosted-engine --upgrade-appliance:

http://www.ovirt.org/develop/release-management/features/hosted-engine-migration-to-4-0/

A suggestion from simone for a better description of this flow is instead of:

-    Set the global maintenance mode
-    Put the host where the engin VM is running into maintenance
-    Add the 4.0 repo and upgrade the host

Maybe something like this:

- Set the global maintenance mode
- set the host in maintenance mode: all the vm but the engine one will migrate away
- stop the engine VM with hosted-engine --vm-shutdown
- upgrade the host with 4.0 packages
- re-start the engine VM on that host with hosted-engine --vm-start