Bug 1327891 - Edit hosted engine vm dialog sends parameters that weren't changed to UpdateVmCommand
Summary: Edit hosted engine vm dialog sends parameters that weren't changed to UpdateV...
Keywords:
Status: CLOSED DUPLICATE of bug 1326810
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
high
urgent vote
Target Milestone: ovirt-3.6.6
: ---
Assignee: Jenny Tokar
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-17 15:15 UTC by Jenny Tokar
Modified: 2016-04-18 15:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-18 15:05:47 UTC
oVirt Team: SLA
rgolan: ovirt-3.6.z?
rgolan: blocker?
mgoldboi: planning_ack+
rgolan: devel_ack+
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Jenny Tokar 2016-04-17 15:15:42 UTC
Description of problem:
When opening the edit vm dialog in the ui and closing it using the "ok" button an error appears that states that a locked field was edited. 
The bug was found on 3.6.6 snapshot. 
It does not reproduce on 3.6.5

Version-Release number of selected component (if applicable): 3.6.6


How reproducible: 3/3


Steps to Reproduce:
1. Have a hosted engine vm.
2. Open the edit vm dialog.
3. Don't change anything and click on "ok". 

Actual results:
An error appears stating a locked field is being edited. 

Expected results:
The dialog should close. The vm shouldn't change in the db. 

Additional info:
The bug can also be reproduced via api (update vm).
After some research it appears that the parameters that are passed to the backend contain some fields that are changed even though nothing was changed.
Those parameters are: dbGeneration, interfaces, quotaEnforcmentType and vmInit. The error is caused due to a change in vmInit. The expected value is null and the received is an empty object.

Comment 1 Jenny Tokar 2016-04-18 15:05:47 UTC

*** This bug has been marked as a duplicate of bug 1326810 ***


Note You need to log in before you can comment on or make changes to this bug.