<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 15, 2016 at 10:33 AM, Renout Gerrits <span dir="ltr"><<a href="mailto:mail@renout.nl" target="_blank">mail@renout.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi All,</div><div><br></div><div>We have an environment which we want to upgrade to ovirt 4.0. This was initially installed at 3.5, then upgraded to 3.6.</div><div>Problem we're facing is that for an upgrade to 4.0 a compatibility version of 3.6 is required.</div><div>When changing the cluster compatibility version of the 'Default' cluster from 3.5 to 3.6 we get the error in the gui: "Cannot change cluster compatibility version when a VM is active. please shutdown all VMs in the cluster."</div><div>Even when we shutdown all vm's, except for the Hosted Engine we get this error.</div><div>On the hosts a 'vdsClient -s 0 list' is done which will return the HE.</div><div>In the engine logs we have the following error: "2016-12-08 13:00:18,139 WARN [org.ovirt.engine.core.bll.<wbr>storage.<wbr>UpdateStoragePoolCommand] (default task-25) [77a50037] CanDoAction of action 'UpdateStoragePool' failed for user admin@internal. Reasons: VAR__TYPE__STORAGE__POOL,VAR__<wbr>ACTION__UPDATE,$ClustersList Default,ERROR_CANNOT_UPDATE_<wbr>STORAGE_POOL_COMPATIBILITY_<wbr>VERSION_BIGGER_THAN_CLUSTERS"</div><div><br></div><div>So problem would be that the HE is in the Default cluster. But how does one change the compatibility version when the HE is down?</div><div>I've tried shutting down the engine, changing the version in the DB: "UPDATE vds_groups SET compatibility_version='3.6';" and starting the engine again.</div><div><br></div><div>When I do that and try to start a VM:</div><div>2016-12-09T13:30:21.346740Z qemu-kvm: warning: CPU(s) not present in any NUMA nodes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15</div><div>2016-12-09T13:30:21.346883Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config</div><div>2016-12-09T13:30:21.355699Z qemu-kvm: "-memory 'slots|maxmem'" is not supported by: rhel6.5.0</div><div><br></div><div>So that change was rolled back to compatibilty 3.5. After that we we're able to start vm's again.</div><div>Please note that all hosts and HE are EL7.</div><div><br></div><div>To me this doesn't seem like a strange set-up or upgrade path. Would it be possible to start the HE in another cluster than Default or is there a way to bypass the vdsClient list check?</div><div>What is the recommended way of upgrading the HE in this case?</div></div></blockquote><div><br></div><div>Please take a look here:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1364557">https://bugzilla.redhat.com/show_bug.cgi?id=1364557</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Kind regards,</div><div>Renout</div></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>