Bug 840006 - [High Availability] Cannot save value for option "Priority for Run" other than Low
Summary: [High Availability] Cannot save value for option "Priority for Run" other tha...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: ---
Assignee: ofri
QA Contact: Pavel Novotny
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-13 12:44 UTC by Pavel Novotny
Modified: 2016-02-10 20:17 UTC (History)
8 users (show)

Fixed In Version: si14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:04:43 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pavel Novotny 2012-07-13 12:44:56 UTC 
Description of problem:
Creating or updating a Server VM: High Availability tab - "Priority for Run/Migration Queue" -> "Low" value is always saved.

Version-Release number of selected component (if applicable):
rhevm-webadmin-portal-3.1.0-6.el6ev.noarch (SI10)

How reproducible:
Always

Steps to Reproduce:
1. RHEVM / VMs tab: create or edit a Server VM
2. On High Availability tab, set "Priority for Run" to Medium or High.
3. Submit changes
  
Actual results:
The VM has set "Priority for Run" still to Low. Your chnanges were not saved.

Expected results:
Your chnanges should be saved.

Additional info:
Regression against rhevm-webadmin-portal-3.0.3_0001-3.el6.x86_64 (IC155.1)
Comment 2 ofri 2012-08-05 08:44:55 UTC 
merged upstream (http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=4aebf5ea7d1d061e47ff8c3a1aef7880df2d28bb)
Comment 3 Pavel Novotny 2012-09-17 12:49:53 UTC 
Verified in rhevm-3.1.0-15.el6ev (SI17).

Followed instructions in reproducer (comment#0).
Verified for new and existing server VM.
Changed value of "Priority for Run/Migration queue" parameter to Medium or High is now saved permanently.
Note You need to log in before you can comment on or make changes to this bug.