<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 29, 2016 at 10:25 AM, <span dir="ltr"><<a href="mailto:mike.lupe@gmx.ch" target="_blank">mike.lupe@gmx.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello all,<br>
<br>
yesterday I upgraded my 3.6.x to 4.0 and got stuck with obviously not being able to shutdown HE VM itself ("shutdown all VMs" required for increasing the compatibility level to 4.0). As I luckily already had a 4th pure computing node, rgolan friendly walked me through the process of creating a new V4 cluster and moving that 4th node to it. The purpose was to free up the default cluster, to be prepared to increase to V4.<br>
<br>
The next step was to migrate the HE VM to the new cluster ("automatically chose host", as there is only one host for that new cluster). Everything went well, but (as rgolan asked to check) the cluster assignment for the HE VM in the edit VM dialogue still shows "Default" and an attempt to increase the compatibility of "Default" cluster of course didn't work ("first shut down all VMs!"). The migration of another VM to that new cluster on the other hand worked without a glitch.<br>
<br>
Attached is the engine.log. Relevant entries should start at around " 2016-06-29 00:53:20 ", it should be the time I created the new cluster and moved pure computing node " slp-ovirtnode-04 " to it. Please ignore the glusterfs brick entries, I have additional disks ready to be added, but this is another story ;)<br>
<br>
Hopefully there is a way to entirely move the HE VM to the new cluster.<br>
<br>
Thanks and regards<br>
mikelupe<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br></blockquote><div><br></div><div>At the end of the migration we prevent that action on the hosted engine vm specifically </div><div> <br></div><div>2016-06-28 21:55:20,734 WARN [org.ovirt.engine.core.bll.ChangeVMClusterCommand] (ForkJoinPool-1-worker-0) [3ce2a3ad] Validation of action 'ChangeVMCluster' failed for user SYSTEM. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM__CLUSTER,ACTION_TYPE_FAILED_CANNOT_RUN_ACTION_ON_NON_MANAGED_VM<br></div><div><br></div><div>I opened <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1351533">https://bugzilla.redhat.com/show_bug.cgi?id=1351533</a></div><div><br></div><div>Mike if you want meanwhile I can supply a script to help you with that. </div><div><br></div><div><br></div></div><br></div></div>