I am sure there would be some challenges there because you cannot delete that vm, its protected... However the rest of your stuff should run just fine. I have never done it myself, most people head the opposite direction.On Thu, Sep 27, 2018 at 8:31 PM Michael Mast <turboaaa@gmail.com> wrote:I figured as much, but wasn't sure if there would be any changes needed to the database so the engine will know it is no longer self hosted.--On Thu, Sep 27, 2018, 20:28 Donny Davis <donny@fortnebula.com> wrote:Use the backup and restore procedure to move your engine maybeOn Thu, Sep 27, 2018 at 4:08 PM Michael Mast <turboaaa@gmail.com> wrote:We had it happen again, but this time on the other host. This started happening not long after I tried to update the engine, and I think I screwed that up. The instructions I was working off of was outdated and a lot of the links on the ovirt site are broken. My theory is that the engines were not "synced" since a copy runs on each host. This would cause the engine on one host to come online and think the other is not responding, at this point it forces the other host offline using iDRAC (This is in the logs how it reboots the other hsot) and forces all VMs over.--So what I did was remove one host from the cluster, re-install CentOS7, and re-add it to the cluster. This way the engine config would be copied from the primary host and keep them synced. If this does not work the next step is to convert the hosted engine into a dedicated engine. Are there any good guides for making this conversion?-Michael Mast_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/2EDXBKVNRMFDYSLP5CHUDMXVZ5NCLXFI/
-Michael Mast