Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146069

Summary:	Online change of host properties for VM does not save correctly for application at power off.
Product:	[oVirt] ovirt-engine	Reporter:	Zordrak <redhat.bugzilla>
Component:	Frontend.WebAdmin	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, dfediuck, ecohen, gklein, lsurette, mgoldboi, michal.skrivanek, rbalakri, rgolan, yeylon
Target Milestone:	---	Flags:	ylavi: planning_ack? ylavi: devel_ack? ylavi: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	sla
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-24 09:18:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zordrak 2014-09-24 11:49:09 UTC

Description of problem:

Virtual Machine running with migration options set to "Allow Manual Migration Only". Changing VM properties, under "Host" section, setting migration option to "Do Not Allow Migration" is not saved. The UI indicates that there is a setting requiring VM reset to apply. However the setting is immediately changed to "Allow Manual and Custom Migration" and when the host is powered off, this remains unchanged. The setting "Do not allow migration" can only be set when the VM is already powered off.

Version-Release number of selected component (if applicable):
3.5-pre (rc2)

How reproducible:
Always so far

Steps to Reproduce:
1. Set VM state to "Allow Manual Migration Only"
2. Start Host
3. Set VM state to "Do not allow migration"
4. Verify state
5. Power off VM
6. Verify state
7. Power on VM
8. Verify state

Actual results:
State set to "Allow Manual and Custom Migration"

Expected results:
State set to "No Migration Allowed"

Additional info:

Comment 1 Doron Fediuck 2014-11-23 15:14:53 UTC

Are you using hosted engine (running the engine inside a VM)?

Comment 2 Zordrak 2014-11-23 20:41:50 UTC

Yes.

Comment 3 Red Hat Bugzilla Rules Engine 2015-10-19 10:55:26 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Sandro Bonazzola 2015-10-26 12:33:14 UTC

this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 5 Sandro Bonazzola 2015-11-05 08:22:00 UTC

oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high

Comment 6 Red Hat Bugzilla Rules Engine 2015-11-16 14:07:38 UTC

This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset.
Please set the correct milestone or add the flag.

Comment 7 Roy Golan 2016-01-24 09:18:28 UTC

This behaviour is under a change. See Bug 1058384

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

Comment 8 Red Hat Bugzilla 2023-09-14 02:48:08 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days