Bug 1367405

Summary:	Cannot set custom compatibility version via UI
Product:	[oVirt] ovirt-engine	Reporter:	sefi litmanovich <slitmano>
Component:	BLL.Virt	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED CURRENTRELEASE	QA Contact:	sefi litmanovich <slitmano>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0.2.6	CC:	bugs, mgoldboi, michal.skrivanek, sgratch, tjelinek
Target Milestone:	ovirt-4.1.0-alpha	Flags:	rule-engine: ovirt-4.1+ mgoldboi: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+
Target Release:	4.1.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-01 14:41:53 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:

Description sefi litmanovich 2016-08-16 11:07:35 UTC

Description of problem:

On new vm/pool menu, both in webadmin and userportal, when setting a value in system tab -> custom compatibility version drop down e.g. 4.0, immediately after setting the value, the menu has a re fresh and the value is set back to None.
This seems to not even get to backend and there are no signs of this problem in any log (engine, server, ui).

Creating a vm/pool with a specific custom compatibility version via API works fine, so the problem seems to be purely UI issue.

The issue doesn't occur when opening the edit vm/pool menu, only upon new vm/pool creation.

Version-Release number of selected component (if applicable):
rhevm-4.0.2.6-0.1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. Open rhevm webadmin and click the new vm button under VMs tab.
2. In system sub-tab in menu under advanced configurations set custom compatibility version to 4.0

Actual results:
menu flickers and the value is overridden and set to None again (blank).

Expected results:
The configured value is set and vm is created successfully.

Additional info:

Comment 1 Tomas Jelinek 2016-08-18 05:49:41 UTC

it is a UI only bug which happens only in new dialog, not in edit, so it does not block any update or anything. Targeting to 4.0.5

Comment 2 Tomas Jelinek 2016-09-12 06:22:57 UTC

There is a nice chance this bug has been fixed as a side effect of: https://gerrit.ovirt.org/#/c/63305
@Sharon, could you please check and if yes, close as duplicate of https://bugzilla.redhat.com/1373204 ?

Comment 3 Sharon Gratch 2016-09-13 11:02:23 UTC

(In reply to Tomas Jelinek from comment #2)
> There is a nice chance this bug has been fixed as a side effect of:
> https://gerrit.ovirt.org/#/c/63305
> @Sharon, could you please check and if yes, close as duplicate of
> https://bugzilla.redhat.com/1373204 ?

I checked on master and the bug was fixed only for 'new pool' dialog.
It was not fixed for 'new vm' dialog, i.e when creating a new vm and setting the custom compatibility version, the menu flickers and the value is set to None.

therefore this bug should be handled and can't be closed.

Comment 4 Tomas Jelinek 2016-10-31 13:22:01 UTC

pushing out of 4.0.z because:
- the patch fixing it is very risky
- a workaround exists (e.g. create a VM and than edit it to change the custom compatibility version)
- no actual harm is done by this bug, it is mostly an annoyance

Comment 5 Red Hat Bugzilla Rules Engine 2016-10-31 13:22:07 UTC

Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Sandro Bonazzola 2016-12-12 14:00:18 UTC

The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 7 sefi litmanovich 2016-12-19 08:43:42 UTC

Verified with ovirt-engine-4.1.0-0.2.master.20161218144454.gitbaa2853.el7.centos.noarch