Description of problem: Migration options must be filled when marking POOL VM as HA Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Create a new VM POOL with 1 VM 2.Edit the created VM 3.Mark the VM as HA 4.Try to save Actual results: The Host TAB is marked with RED and when you open it it marks the Migration Options field with RED (see attached images) Expected results: Should work and save HA setting as is done for VM that is not in pool Additional info: Setting HA for a VM that is not in a POOL works fine
Created attachment 922067 [details] screenshot
Changing the subject since a POOL VM should not be set to HA at all. So the problem is that if we edit the POOL VM after POOL creating, we have the ability to select the HA TAB for that VM
It is not very clear from this bug what was the decided solution for this problem.. I tried some flows, please let me know if this is the expected behaviour and we should re open or open a new one: 1. In all cases there's no ability to create/edit a vmPool as HA. 2. In a specific VM in the pool you can change to HA regardless to Migration Options. This seems as expected. As for the 'Use Custom migration downtime' option, behaviour is a bit strange I think: 1. Create VMpool without defining 'Use Custom migration downtime': this result in vm inheriting this configuration. If you edit the VM and mark this checkbox, the value box is still gray so you can not define a value, and after confirming no error or red mark appears but if you edit VM again you see checkbox unmarked. 2. Create VMpool and define 'Use Custom migration downtime' + some value x: this result in vm inheriting this configuration. If you edit the VM the checkbox is marked and the value from pool is there. If you uncheck the box and confirm, next time you edit the VM the behaviour is similar to (1) - meaning you cannot re-check the box. I wonder if this is the wanted logic behind this configuration or maybe it's a GUI bug.. please let me know what you think.
I forgot to mention in previous comment, this was tested with ovirt-engine-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch.
Sefi this is not related to HL VMs as the bug state, This is a validation error as you can see in the attached screenshot that Eli posted. "Use custom migration downtime" field not meant to be changeable in Pool and the patch set it to unchangeable.
Verified with 3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch according to flow specified on comment 3 and shahar's comment 5. Please advise whether another bz should be opened regarding the 'Use Custom migration downtime' behaviour also mentioned on comment 3.
(In reply to sefi litmanovich from comment #6) Yes, I suppose a different one for the he 'Use Custom migration downtime' behavior
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.