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

Bug 1067513

Summary: RHEV do not allow to change "Run on" parameter for running guests.
Product: Red Hat Enterprise Virtualization Manager Reporter: Pratik Pravin Bandarkar <pbandark>
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, ecohen, iheim, michal.skrivanek, Rhev-m-bugs, sputhenp, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: All   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-28 10:00:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error none

Description Pratik Pravin Bandarkar 2014-02-20 15:00:09 UTC 
Description of problem:
in 3.3 if we try to change the "host --> Start Running on specific host"  option for running vm then it fail with an error "There was an attempt to change VM values while the VM is not down. Please shut down the VM in order to modify these properties." 

Which was allowed in 3.2

Version-Release number of selected component (if applicable):
rhevm-3.3.0-0.46.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1.Run vm
2.Edit.
3.Show Advanced Option --> Host --> Start running on --> Select "Specific".
4. click on OK.

Actual results:
Operation will fail with an error(attached screenshot):
---
There was an attempt to change VM values while the VM is not down. Please shut down the VM in order to modify these properties.
---

Expected results:
As its allowed in 3.2, rhev3.3 should allow to change the property.

Additional info:
Comment 1 Pratik Pravin Bandarkar 2014-02-20 15:01:51 UTC 
Created attachment 865563 [details]
error
Comment 3 Michal Skrivanek 2014-02-28 10:00:15 UTC 

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