[ovirt-users] Restoring Hosted Engine to failed

[Logan Kuhn]

Logs as Yedidyah requested are attached.  There was nothing in /tmp/ovirt*
on the host.  The host should be ovirttest1 in the logs

I saw that those options existed, but unfortunately the decision was made
to stay on 4.0.6 for now since other than this we have been quite pleased
with it.

With that said, I do know for certain the previous environment wasn't in
global maintenance before that backup was taken.  Does that mean it's not
viable or can we make some database modifications to clean it up?

Logan


On Sun, Feb 26, 2017 at 5:00 AM, Simone Tiraboschi <stirabos at redhat.com>
wrote:

>
>
> On Sun, Feb 26, 2017 at 8:02 AM, Yedidyah Bar David <didi at redhat.com>
> wrote:
>
>> On Fri, Feb 24, 2017 at 6:34 PM, Logan Kuhn <support at jac-properties.com>
>> wrote:
>> > Hi
>> >
>> > I'm in the process of trying to restore our previous hosted engine onto
>> new,
>> > permanent, storage.  I've followed this guide:
>> > https://www.ovirt.org/develop/developer-guide/engine/migrate
>> -to-hosted-engine/
>
>
> The point is that the DB you restored contains references to the
> hosted-engine storage domain and to the engine VM you used on your initial
> hosted-engine env.
> You have to clean up these references to let the engine correctly import
> the new hosted-engine env.
> With 4.1 we introduced two new options to engine-backup in order to make
> correctly working for a backup took on a previous hosted engine env, they
> are:
>  --he-remove-storage-vm             Removes the hosted-engine storage
> domain, all its entities and the hosted-engine VM during restore.
>  --he-remove-hosts                  Removes all the hosted-engine hosts
> during restore.
>
> Hosted-engine host should be redeployed as well since they point to the
> previous env as well.
>
> The correct path to migrate from a previous hosted-engine env to a new one
> is:
> - set global maintenance mode on the previous env
> - set maintenance mode for the hosted engine hosts on the previous engine
> - take the backup of the previous engine
> Follow https://www.ovirt.org/develop/developer-guide/
> engine/migrate-to-hosted-engine/ adding  '--he-remove-storage-vm
>  --he-remove-hosts ' to the DB restore command.
>
>
>
>> > It went pretty smoothly up until the hosted engine deploy tried to add
>> the
>> > host to the environment. The error was Unable to add HEVM to the
>> manager.
>> > However, I can login to the environment just fine, but it does not have
>> the
>> > HEVM and the host it's currently running on is down.
>> >
>> > I've attached the hosted engine setup log.  Let me know if there are any
>> > other logs that will be helpful
>>
>> Please check/share also: From the engine:
>> /var/log/ovirt-engine/engine.log
>> /var/log/ovirt-engine/host-deploy/*
>>
>> From the host:
>> /var/log/vdsm/vdsm.log
>> /tmp/ovirt* (if found. If all is ok they are copied to engine and removed)
>>
>> Best,
>>
>> >
>> > Logan
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users at ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>>
>> --
>> Didi
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170226/e3e92edf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logsforyedidyah.tar.gz
Type: application/x-gzip
Size: 1842179 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170226/e3e92edf/attachment-0001.gz>