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

Bug 1093281

Summary: Unable to change the VMs "Migration Property" while VM is in the running state.
Product: Red Hat Enterprise Virtualization Manager Reporter: Udayendu Sekhar Kar <ukar>
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: acathrow, dfediuck, ecohen, gklein, iheim, Rhev-m-bugs, rpai, yeylon
Target Milestone: ---   
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: 2014-05-08 12:18:47 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 Udayendu Sekhar Kar 2014-05-01 07:10:15 UTC
Description of problem:
If a VM is running with "allow manual migration only" migration property then its not going to allow to alter it to "allow manual and automatic migration" and to select the "HA" check box.

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


How reproducible:
100%

Steps to Reproduce:
1. Create a VM with "allow manual migration only" option and start the VM
2. Once the VM wil start, try to change the migration property to "allow manual and automatic migration"
3. It will fail and due to this its not possible to make the VM as 'HA'

Actual results:
If the VM is in the running state with "allow manual migration only" as the migration property, its not possible to change the VMs migration property and fail to mark it as a HA.


Expected results:
Through the VM is in the running state, It should allow to change the VMs migration policy and HA mode.

Comment 1 Doron Fediuck 2014-05-08 12:18:47 UTC

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