Bug 1275778
| Summary: | Unable to set VM highly available in Instance type | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Vladimir Astafiev <v.astafiev> | ||||
| Component: | Frontend.WebAdmin | Assignee: | Tomas Jelinek <tjelinek> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | sefi litmanovich <slitmano> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.6.0.2 | CC: | bugs, dfediuck, joerg.br, mavital, mgoldboi, rgolan, sbonazzo, slitmano, tjelinek | ||||
| Target Milestone: | ovirt-3.6.5 | Flags: | rule-engine:
ovirt-3.6.z+
mgoldboi: planning_ack+ tjelinek: devel_ack+ mavital: testing_ack+ |
||||
| Target Release: | 3.6.5 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-04-21 14:35:47 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Bug partially reproduced on rhevm-3.6.3.4-0.1.el6.noarch: 1. Created a custom instance and Set Host -> Allow manual and automatic migration Set High Availability -> Highly Available (tried with all 3 priorities) 2. Edited the 'small' instance and Set Host -> Allow manual and automatic migration Set High Availability -> Highly Available (tried with all 3 priorities) 3. Create a vm from the custom instance. 4. Create a vm from 'small' instance. Result -> In both cases the VMs created from the instance was set to Highly available exactly as was defined in the instance so this part is working fine. The part that does reproduce is that when I edit again the custom and 'small' instances, the Highly available check-box is unchecked, BUT the priority is still set as last time I edited, and even if I don't "re check" the box, and keep it the same, if I create another vm it is marked as highly available.. so my guess is that the only bug here is a GUI bug, since the box should be checked in the edit instance type menu. Can only verify partially. Cannot verify with new instance type flow due to instance type creation bug: https://bugzilla.redhat.com/show_bug.cgi?id=1323493. Verified with Edit instance type flow. Let me know if we can verify this or we should wait for next build until the instance type bug is fixed to verify. As the flow is the same once the instance type is created, it makes no real difference if the instance type is new or existing.. so I mark this bz as verified. This was tested on rhevm-3.6.5-0.1.el6.noarch. |
Created attachment 1086945 [details] engine.log messages Version-Release number of selected component (if applicable): oVirt Engine Version: 3.6.0.2-1.el7.centos How reproducible: Always Steps to Reproduce: 1. Create/Edit Instance Type 2. Set Host -> Allow manual and automatic migration Set High Availability -> Highly Available 3. Press OK Actual results: VMs created from this instance is not highly available, option in instance is not checked Expected results: VMs created from this instance is highly available, option in instance type is checked Additional info: I found this problem after upgrade from RC1 to RC3