Bug 1698334

Summary:	Migration configuration doesn't work for HE VM - values are locked.
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	BLL.HostedEngine	Assignee:	Andrej Krejcir <akrejcir>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.2.1	CC:	akrejcir, bugs, rbarry
Target Milestone:	ovirt-4.3.4	Keywords:	AutomationBlocker
Target Release:	4.3.4.1	Flags:	pm-rhel: ovirt-4.3+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.4.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-11 06:24:04 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 Polina 2019-04-10 07:29:03 UTC

Description of problem: Now migration options are available for HE VM (in Web UI), but actually don't work. An attempt to configure brings error - "There was an attempt to change Hosted Engine VM values that are locked"


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


How reproducible:


Steps to Reproduce:
1. Open Edit window for HE VM and choose 'Manual migration'.
2.
3.

Actual results:
"Error while executing action: 
HostedEngine:
There was an attempt to change Hosted Engine VM values that are locked"

Expected results: if these options are able for HE VM in Web UI, they must work. Otherwise, it must be disabled. If we treat HE VM as a VM (as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1583968#c4), I think migration configuration must work. The user can't prevent balancing of the HE VM by configuring manual migration.

Additional info:

Comment 1 Polina 2019-05-20 19:41:18 UTC

verified on ovirt-engine-4.4.0-0.0.master.20190519192123.gitd51360f.el7.noarch

Comment 2 Sandro Bonazzola 2019-05-22 07:11:56 UTC

This bug fix is targeted to 4.3.5 but referenced patches are already included in 4.3.4. Can you please check and eventually adjust target milestone?

Comment 3 Polina 2019-05-26 06:34:51 UTC

verified on the base of https://bugzilla.redhat.com/show_bug.cgi?id=1698334#c2

Comment 4 Sandro Bonazzola 2019-06-11 06:24:04 UTC

This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.