<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 17-3-2017 20:33, Michal Skrivanek
      wrote:<br>
    </div>
    <blockquote
      cite="mid:ECD74CFA-F01A-470D-859B-0E1522C77B90@redhat.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br class="">
      <div>
        <blockquote type="cite" class="">
          <div class="">On 17 Mar 2017, at 11:55, jvdwege &lt;<a
              moz-do-not-send="true" href="mailto:jvdwege@xs4all.nl"
              class=""><a class="moz-txt-link-abbreviated" href="mailto:jvdwege@xs4all.nl">jvdwege@xs4all.nl</a></a>&gt; wrote:</div>
          <br class="Apple-interchange-newline">
          <div class="">
            <meta http-equiv="Content-Type" content="text/html;
              charset=windows-1252" class="">
            <div style="font-size: 10pt; font-family:
              Verdana,Geneva,sans-serif" class="">
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace">As per the subject I'm trying to
                upgrade my ovirt install and sofar the upgrade has been
                smooth.<br class="">
                I'm running hosted-engine in Centos7.3 and my hosts are
                running Fedora24 now with ovirt-4.1<br class="">
                If I try to upgrade my cluster from version 3.6 to 4.0
                or 4.1 I receive an error message and can't find a
                solution using google. First I get the following
                message:<br class="">
                <br class="">
                <span style="font-family: courier
                  new,courier,monospace;" class="">All running VMs will
                  be temporarily reconfigured to use the previous
                  cluster compatibility version and marked pending
                  configuration change.</span><br class="">
                <span style="font-family: courier
                  new,courier,monospace;" class=""> In order to change
                  the cluster compatibility version of the VM to a new
                  version, the VM needs to be manually shut down and
                  restarted.</span><br class="">
                <span style="font-family: courier
                  new,courier,monospace;" class=""> There are 1 running
                  VM(s) affected by this change.</span><br class="">
                <br class="">
                <span style="font-family: courier
                  new,courier,monospace;" class=""> Are you sure you
                  want to change the Cluster Compatibility Version?</span><br
                  class="">
                <br class="">
                Yes, I want to change version :-) so I click OK</div>
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace">I then get the following error
                message:</div>
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace"> </div>
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace"><span style="font-family:
                  courier new,courier,monospace;" class="">Error while
                  executing action: </span><br class="">
                <br class="">
                <ul style="margin-top: 0;" class="">
                  <li class=""><span style="font-family: courier
                      new,courier,monospace;" class="">Cannot edit
                      Cluster. Illegal number of monitors is provided,
                      max allowed number of monitors is 1 for VNC and
                      the max number in the ValidNumOfMonitors
                      configuration variable for SPICE.</span></li>
                  <li class=""><span style="font-family: courier
                      new,courier,monospace;" class="">Cannot edit VM.
                      Illegal number of monitors is provided, max
                      allowed number of monitors is 1 for VNC and the
                      max number in the ValidNumOfMonitors configuration
                      variable for SPICE.</span></li>
                </ul>
              </div>
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace"> </div>
              <div class="pre" style="margin: 0; padding: 0;
                font-family: monospace">Anyone has seen this before and
                is able to help?</div>
            </div>
          </div>
        </blockquote>
        <div><br class="">
        </div>
        Is that an old VM, perhaps from 3.5 or even earlier? Has it been
        restarted since? Can you shut it down now and rerun after the
        cluster change? That would likely be the most simple resolution.</div>
      <div>If there are troubles even after the VM is Down try to edit
        and swithc console from VNC to SPICE or vice versa and run again</div>
      <div><br class="">
      </div>
      <br>
    </blockquote>
    The problem is that it is the hosted-engine itself that is blocking
    the upgrade. There is only one VM running but maybe there is one of
    the shutdown VMs that is blocking this. Will have a look at all of
    them and save their config to see if that helps.<br>
    <br>
    Thanks,<br>
    <br>
    Joop<br>
    <br>
  </body>
</html>