This is a multi-part message in MIME format.
--------------060903020405030107030502
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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
<mailto:rgolan@redhat.com>> wrote:
On Mon, Jan 4, 2016 at 1:08 PM, Stefano Danzi
<s.danzi(a)hawai.it <mailto:s.danzi@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.
--------------060903020405030107030502
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">Il 04/01/2016 12.28, Gianluca Cecchi ha
scritto:<br>
</div>
<blockquote
cite="mid:CAG2kNCzN53OuU14uf9jOJXkQWnXZAA7zW0C5MPib1VS5PwRQzA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Jan 4, 2016 at 12:20 PM, Roy
Golan <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:rgolan@redhat.com"
target="_blank">rgolan(a)redhat.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Mon, Jan 4, 2016 at 1:08 PM,
Stefano Danzi <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:s.danzi@hawai.it"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:s.danzi@hawai.it">s.danzi@hawai.it</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Hi !<br>
After upgrade from ovirt 3.5 to
3.6 I'm not able to manually start
hosted-engine vm using
"hosted-engine --vm-start"<br>
<br>
I have only one host.<br>
I put engine in global maintenance
mode, I shutdown all VM and hosted
engine VM.<br>
I reboot the host and run
"hosted-engine --vm-start", but
the VM never start (I waited for
10 minutes).<br>
When I run " hosted-engine
--set-maintenance --mode=none"
engine VM start immediately.<br>
<br>
</blockquote>
</div>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Sorry I was quick to answer and now I saw you
already tried and it immediately started the vm.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Possibly the original question was of different kind?</div>
<div>So how to manually start engine VM if environment is in
global maintenance and I have previously shutdown it?
Should it be possible?</div>
<div>For example one wants to check it from an OS point of
view and not oVirt point of view, before exiting
maintenance...</div>
<div><br>
</div>
<div>Gianluca </div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">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.
</pre>
</body>
</html>
--------------060903020405030107030502--