Created attachment 1310034 [details] logs and screenshots Description of problem: I tried to change the compatibility level on our cluster from 4.0 to 4.1 and failed the following error message: Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [XXXXXXXlong list of vmsXXXXXXXXX] with incorrect configuration. To fix the issue, please go to each of them, edit and press OK. If the save does not pass, fix the dialog validation. when you edit the vm and click ok the configuration is saved and no error appears. engine log shows the reason for failure is macspool in special properties: 2017-08-07 14:44:17,395+03 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-87) [2697f1d1] Validation of action 'UpdateVm' failed for user dron. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVAL ID_CUSTOM_PROPERTIES_INVALID_KEYS,$MissingKeys macspoof + there is a spelling error in the word 'dialog' Version-Release number of selected component (if applicable): ovirt-engine-4.1.4.2-0.1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. create vms with custom property 'macspoof' 2. upgrade rhv from 4.0 to 4.1.4 3. change cluster compatibility from 4.0 to 4.1 4. after the error message is presented -> navigate to vms tab -> edit the vm -> press ok Actual results: There is no error message presented in the vm to suggest what is the configuration issue with the vm Expected results: we should suggest to the user a way to solve this issue so either the cluster upgrade or the edit of the vm should suggest a problem with the cluster properties. Additional info: attaching engine log and screenshots 2017-08-07 14:44:17,395+03 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-87) [2697f1d1] Validation of action 'UpdateVm' failed for user dron. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVAL ID_CUSTOM_PROPERTIES_INVALID_KEYS,$MissingKeys macspoof
@Dafna: so after you have updated the VM manually, was it's configuration correct? Because I have a suspicion that yes - it dropped the incorrect custom property. During the update cluster, the detailed error messages are supposed to be in auditlog but unfortunately due to https://bugzilla.redhat.com/show_bug.cgi?id=1432127 they are not.
After I pressed edit -> OK nothing was removed from the configuraion and I was still bocked from the upgrade. I had to manually remove the custom property in order to continue with the upgrade.
right, because you were still in the old cluster. To simulate the error you would have to set the custom compatibility for the VM to the new one. But anyway, the core problem here is that the audit log does not contain the error messages which is 1432127. Closing this as duplicate of that one. *** This bug has been marked as a duplicate of bug 1432127 ***