OK, if the icon is there that is a good thing. There would be no icon if you didn't select deploy. Its not terribly obvious when first installing a second host that it needs the deploy part set.
There's something else causing the engine migration to fail. You can dig through the logs on the engine and hosts. I would look next at the underlying storage for the ovirt-engine image to see if it got bit by the bug that leaves it owned by root and not vdsm:kvm. That prevented me from migrating engine to properly deployed nodes when upgrading to 4.3 On one of the hosts, follow the path /rhev/data-center/mnt/* to "ls -l" the images directory for your hosted-storage and check the ownership. If its owned by root and not vdsm:kvm then chown it to that (aka 36:36) and try migrating again. On Mon, Feb 25, 2019 at 10:50 PM <k...@intercom.pro> wrote: > The crown icon on the left of the second host is gray. When I try to > migrate the engine, I get the error: > > Migration of VM 'HostedEngine' to host 'ovirt2' failed: VM destroyed > during the startup > EVENT_ID: VM_MIGRATION_NO_VDS_TO_MIGRATE_TO(166), No available host was > found to migrate VM HostedEngine to. > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/NHG7MBNCPYMSXC7PGYWIZ6WEDT2Y6LYU/ >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RTSYZ7CKQDASLYSLG4YTBICTFZH3E7UA/
