Error setting cluster level to 4.2
Hello, after upgrading engine (external) and the 3 hosts composing the cluster, I try to set its level to 4.2 but I receive this kind of message " Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [ov42, ovlive3, ovlive4, ovlive1, ovlive2] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change. " The ovliveN VMs are diskless where I boto from the oVirt live iso for testing and ov42 a nested single VM where I tested the oVirt 4.2 environment before upgrade of the real cluster. I suspect that the problem could be related with macspoof custom property set to true. Is this? In case how can I manage this sort of problem? Can't I have macspoof in 4.2? Thanks, Gianluca
On 24 May 2018, at 17:13, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, after upgrading engine (external) and the 3 hosts composing the cluster, I try to set its level to 4.2 but I receive this kind of message
" Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [ov42, ovlive3, ovlive4, ovlive1, ovlive2] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change. "
The ovliveN VMs are diskless where I boto from the oVirt live iso for testing and ov42 a nested single VM where I tested the oVirt 4.2 environment before upgrade of the real cluster.
I suspect that the problem could be related with macspoof custom property set to true. Is this? In case how can I manage this sort of problem?
so what does the dialog validation say?
Can't I have macspoof in 4.2?
not sure, but isn’t it only that a custom property is not defined for 4.2 cluster level. For those you need to do that in every version, basically
Thanks,
Gianluca _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org
On Thu, May 24, 2018 at 5:44 PM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote: [snip]
Can't I have macspoof in 4.2?
not sure, but isn’t it only that a custom property is not defined for 4.2 cluster level. For those you need to do that in every version, basically
Correct! thanks ;-) [root@ovmgr1 ~]# engine-config -g UserDefinedVMProperties UserDefinedVMProperties: version: 3.6 UserDefinedVMProperties: version: 4.0 UserDefinedVMProperties: macspoof=true version: 4.1 UserDefinedVMProperties: version: 4.2 [root@ovmgr1 ~]# [root@ovmgr1 ~]# engine-config -s "UserDefinedVMProperties=macspoof=true" Please select a version: 1. 3.6 2. 4.0 3. 4.1 4. 4.2 4 [root@ovmgr1 ~]# engine-config -g UserDefinedVMProperties UserDefinedVMProperties: version: 3.6 UserDefinedVMProperties: version: 4.0 UserDefinedVMProperties: macspoof=true version: 4.1 UserDefinedVMProperties: macspoof=true version: 4.2 [root@ovmgr1 ~]# [root@ovmgr1 ~]# systemctl restart ovirt-engine And then I was able to update the cluster and DC level to 4.2 I will investigate the vNic profile suggestion of SImone, too. Gianluca
On Thu, May 24, 2018 at 5:13 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, after upgrading engine (external) and the 3 hosts composing the cluster, I try to set its level to 4.2 but I receive this kind of message
" Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [ov42, ovlive3, ovlive4, ovlive1, ovlive2] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change. "
The ovliveN VMs are diskless where I boto from the oVirt live iso for testing and ov42 a nested single VM where I tested the oVirt 4.2 environment before upgrade of the real cluster.
I suspect that the problem could be related with macspoof custom property set to true. Is this? In case how can I manage this sort of problem?
If you try to edit the single VM/template you will get a detailed error message with the wrong value.
Can't I have macspoof in 4.2?
Now it's a lot easier: you don't need a vdsm hook for that. You can simply create a custom vNic profile on your logical network and editing it you will be able to remove the vdsm-no-mac-spoofing filter; then you will be able to assign that vNic profile to the interfaces of your VMs.
Thanks,
Gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org
participants (3)
-
Gianluca Cecchi -
Michal Skrivanek -
Simone Tiraboschi