<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 4, 2016 at 1:37 PM, Stefano Danzi <span dir="ltr">&lt;<a href="mailto:s.danzi@hawai.it" target="_blank">s.danzi@hawai.it</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
    <br>
    <br>
    <div>Il 04/01/2016 12.28, Gianluca Cecchi ha
      scritto:<br>
    </div>
    <blockquote 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">&lt;<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@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>
                        <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">&lt;<a href="mailto:s.danzi@hawai.it" target="_blank"></a><a href="mailto:s.danzi@hawai.it" target="_blank">s.danzi@hawai.it</a>&gt;</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&#39;m not able to manually start
                                      hosted-engine vm using
                                      &quot;hosted-engine --vm-start&quot;<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
                                      &quot;hosted-engine --vm-start&quot;, but
                                      the VM never start (I waited for
                                      10 minutes).<br>
                                      When I run &quot; hosted-engine
                                      --set-maintenance --mode=none&quot;
                                      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>
    </div></div><pre 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 &quot;WaitingForLaunch&quot; until cluster exit from maintenance. 



</pre>
  </div>

</blockquote></div><br></div><div class="gmail_extra">in 3.6 maintenance means we can&#39;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&#39;t <br></div><div class="gmail_extra">achieve maintenance action like yum update of sanlock, vdsm, agent , if the the whole system is up.<br><br></div><div class="gmail_extra">Simone, Martin any additions?<br></div></div>