[ovirt-users] Ovirt 3.6.x upgrade to 4.0: HE VM not shutdownable - hyperkonverged r3a1 setup

[Roy Golan]

On Thu, Jun 30, 2016 at 12:33 PM, Roy Golan <rgolan at redhat.com> wrote:

>
>
> On Wed, Jun 29, 2016 at 10:25 AM, <mike.lupe at gmx.ch> wrote:
>
>> Hello all,
>>
>> 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.
>>
>> 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.
>>
>> 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 ;)
>>
>> Hopefully there is a way to entirely move the HE VM to the new cluster.
>>
>> Thanks and regards
>> mikelupe
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
> At the end of the migration we prevent that action on the hosted engine vm
> specifically
>
> 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
>
> I opened https://bugzilla.redhat.com/show_bug.cgi?id=1351533
>
> Mike if you want meanwhile I can supply a script to help you with that.
>
>
>
```bash
su - postgres
psql engine -c "update vm_static set cluster_id = (select cluster_id from
cluster where name = 'NEWCLUSTERNAME') where vm_name = 'HostedEngine';
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160704/439e5101/attachment-0001.html>