Hide Forgot
Description of problem: When we are running optimizer on cluster with VMs that are running on specific host and does not have migration allowed. Optimizer suggest solution of migrating VMs with status: Status: Solution is not doable! There are hard constraint violations. That is nice, but I have no idea what hard constraint I any of my multiple VM are is violated. Better solution is to let optimizer know he should not suggest migrating these VMs. Or suggest user to allow migration on this VM. This is also accaptable as there will be no big change to rules. Version-Release number of selected component (if applicable): 0.4.5 How reproducible: 100% Steps to Reproduce: 1. 2 hosts blue, purple, 4 vms vm1-4 pinned to blue, migration not allowed on VMs 2. Cluster policy - None 3. See optimizer result Actual results: Status: Solution is not doable! There are hard constraint violations. No VM starts are requested at this moment. Migration / Start steps vm3 → purple Target state host vm memory [all in GB] used available purple 2.0 7.7 vm3 2.0 2.0 blue 6.0 7.7 vm-4 2.0 2.0 vm2 2.0 2.0 vm1 2.0 2.0 Expected results: Either new rule for optimizer so it won't try to optimizer cluster but migrating unmigratable VMs or New ui-plugin step that suggests making VM migratable. Additional info: I've got some spammed debug log of optimizer so If necessary, it won't be a problem. :)
Optimizer uses probability based algorithms. So if there is no solution it gives you the best it has and tells you that it is not valid as a whole. Optimizer already has rules that consider a migration of pinned VM to be hard constraint violation. That is why it was able to tell you that in the fist place. The only change that can be done here is to make it more obvious that the solution is not valid. I do not have a per step score so I can't highlight the issue easily. I could implement a new Explain button, that would (on demand) compute the score step by step and display it somehow. It is expensive in terms of cpu/memory though.
*** This bug has been marked as a duplicate of bug 1173551 ***
This is not the some bug, This bug is that the optimizer suggest migrating VMs which does not allow migration. The other bug is that the Optimizer should not propose steps if solution is not doable.
verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.0-0.18.el6
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0427.html