Description of problem: The page at http://www.ovirt.org/Migrate_to_Hosted_Engine is missing critical information about prerequisites which are necessary to follow the instructions. In particular, it does not introduce the fact that the database being utilized is remote from the engine. The instructions will not work unless this is the case. Since remote database is not a default configuration, it is particularly misleading to not mention this. In the example, the database resides on a machine called "didi-lap", which is never introduced. If you do not have a remote database, you will get all the way to Part 2 step "engine-backup --mode=restore ..." before discovering that you are unable to proceed since the restore assumes an existing database is in place. At that point it may be too late to go back (in my case, I had already re-purposed my Hypervisor node for Self-Hosted). At the very beginning under "Preparations" it should state that a remote database resides on didi-lap. If directions could be added for how to create a database which can be utilized for engine-backup --mode restore, that would be very helpful so people without remote databases could also use these instructions. Since these are the only instructions at this time regarding migration to Hosted, it's critical that it be clear and accurate.
Moving pending bugs not fixed in 3.5.0 to 3.5.1.
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant.
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still an issue.