Ovirt upgrade from 4.1 to 4.2

yum clean all
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
yum-config-manager --save --setopt=ovirt-4.1-centos-gluster38.skip_if_unavailable=true
yum-config-manager --save --setopt=ovirt-centos-ovirt41.skip_if_unavailable=true



And finally:

yum update

Again lustre upgrade troubles: unable to mount after upgrade to 2.10.x

The failure is following:

LDISKFS-fs (sda): Unrecognized mount option "context="unconfined_u:object_r:user_tmp_t:s0"" or missing value

But Selinux is disabled so we should remove that mount options.
To fix it:

tunefs.lustre --mountfsoptions="user_xattr,errors=remount-ro" /dev/sda

mount a expected.

After upgrade Ovirt 4.1.3 to 4.1.4 failing to start or migrate the virtual machines

 After upgrade Ovirt 4.1.3 to 4.1.4 it was failing to start  or migrate the virtual machines
 General command validation failure

2017-07-31 17:25:38,078+02 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (default task-497) [949b0e76-a2a9-4978-9879-9d38fc12b77c] Error during ValidateFailure.: java.lang.NullPointerException

the server.log was logging following errors as well:

2017-07-31 17:28:16,228+02 INFO  [org.quartz.core.JobRunShell] (DefaultQuartzScheduler8) Job DEFAULT.org.ovirt.engine.core.bll.scheduling.SchedulingManager.performLoadBalancing#-9223372036854775697 threw a JobExecutionException: : org.quartz.JobExecutionException: failed to execute job
    at sun.reflect.GeneratedMethodAccessor259.invoke(Unknown Source) [:1.8.0_141]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
    at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
    at org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:83) [scheduler.jar:]
    at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:55) [scheduler.jar:]
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_141]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_141]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
    at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]

To fix:

It is turning out that upgrade process was resetting the Scheduling Policy to NULL or none.
 
Edit Cluster->Scheduling Policy-> Select Policy: vm_evently_distributed