Bug 1144810 - 'Do not allow migration' under vm migration options should block vm migration
Summary: 'Do not allow migration' under vm migration options should block vm migration
Keywords:
Status: CLOSED DUPLICATE of bug 1124449
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-21 09:20 UTC by Raz Tamir
Modified: 2016-02-10 20:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-22 06:40:17 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdsm and engine logs (1.16 MB, application/octet-stream)
2014-09-21 09:20 UTC, Raz Tamir 		no flags Details
View All

Description Raz Tamir 2014-09-21 09:20:37 UTC 
Created attachment 939725 [details]
vdsm and engine logs

Description of problem:
In edit tab under vm view, in host sub tab, there is an 'Migration Options' to allow the option to disable migration, this operation follows with the message 
"Some of the changes will be applied after the NEXT RESTART."


Version-Release number of selected component (if applicable):
vdsm-4.16.3-3.el7.beta.x86_64
rhevm-3.5.0-0.11.beta.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. edit vm's host's migration options to 'Do not allow migration'
2. restart the vm
3. try to migrate the vm

Actual results:
operation should be blocked

Expected results:
vm migrates 

Additional info:
Comment 1 Omer Frenkel 2014-09-22 06:25:30 UTC 
Im not sure why migrationSupport is marked for update after restart
Comment 2 Omer Frenkel 2014-09-22 06:40:17 UTC 
sorry re-reading this, the bug is that the changes are not applied even after restart...
we already have a fix pending for that, see bug 1124449

*** This bug has been marked as a duplicate of bug 1124449 ***
Note You need to log in before you can comment on or make changes to this bug.