On Mon, Jan 4, 2016 at 1:37 PM, Stefano Danzi <s.danzi(a)hawai.it> wrote:
Il 04/01/2016 12.28, Gianluca Cecchi ha scritto:
On Mon, Jan 4, 2016 at 12:20 PM, Roy Golan <rgolan(a)redhat.com> wrote:
>
>
>
>>
>> On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi < <s.danzi(a)hawai.it>
>> s.danzi(a)hawai.it> wrote:
>>
>>> Hi !
>>> After upgrade from ovirt 3.5 to 3.6 I'm not able to manually start
>>> hosted-engine vm using "hosted-engine --vm-start"
>>>
>>> I have only one host.
>>> I put engine in global maintenance mode, I shutdown all VM and hosted
>>> engine VM.
>>> I reboot the host and run "hosted-engine --vm-start", but the VM
never
>>> start (I waited for 10 minutes).
>>> When I run " hosted-engine --set-maintenance --mode=none" engine
VM
>>> start immediately.
>>>
>>>
>>
>
> Sorry I was quick to answer and now I saw you already tried and it
> immediately started the vm.
>
>
>
Possibly the original question was of different kind?
So how to manually start engine VM if environment is in global maintenance
and I have previously shutdown it? Should it be possible?
For example one wants to check it from an OS point of view and not oVirt
point of view, before exiting maintenance...
Gianluca
Gianluca you are right!!!
ovirt 3.5 permit to start engine VM when cluster is in maintenance... I did it many
times!!! From oVirt 3.6 it is no longer possible.
VM remain in state "WaitingForLaunch" until cluster exit from maintenance.
in 3.6 maintenance means we can't run the vm. Running it means we needs its
disks available, meaning we need the domain up and monitored and with a
sanlock monitoring it. We can't
achieve maintenance action like yum update of sanlock, vdsm, agent , if the
the whole system is up.
Simone, Martin any additions?