Description of problem: I upgraded our oVirt engine (and hosts) from 4.1 to 4.2.1. After the upgrade I've noticed that the VM affinity rules I've specified are no longer respected. When I edit the affinity group, the VM affinity rule shows 'disabled'. I can change it to 'negative' and save it. But when I click edit again it shows disabled again. The rules are also not respected by the scheduler as both VM's in the group are started on the same host when powered down/up again. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Set soft negative affinity rules for 2 VM's 2. Boot the 2 VM's 3. Actual results: Both VM's are running on the same host Expected results: VM's running on different hosts. Additional info: It seems the properties can no longer be changed.
*** This bug has been marked as a duplicate of bug 1540955 ***