Hi,
The problem is solved, the option to make VM start automatically is to set it high available, and yes I've solved the same issue with infra vm during my first days here.
Best regards.
Hi,I understood we have to put hosted-engine into maintenance mode and shutdown the VMs if we want to power off the host (otherwise it will reboot). I'm setting up a process to- put the HestedEngine in global maintenance mode (hosted-engine --set-maintenance --mode=global)- shutdown the HostedEngine (hosted-engine --vm-shutdown)- PowerOff the HostedEngine (hosted-engine --vm-poweroff)- Power off the server (shutdown -P)Everything works fine and I can start the server back up, remove the HostedEngine from maintenance mode, and it will start automatically running. The issue is when bringing up hosted-engine: all VMs come up but one (BigIP) and I am trying to see if there is way to bring it up without having to store the engine password (using the ovirt_vm API).At the moment, I am having to look for the BigIP VM and then use credentials to bring it up: it will not come up with 'hosted-engine --vm-start'Is there to make this specific VM start the same time as the others VM automatically when HostedEngine starts?Thanks for your help.Regards,Eugène NG--LesCDN------------------------------------------------------------Aux hommes il faut un chef, et au chef il faut des hommes!
L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!