Bug 985320

Summary: Cannot set protocol to SPICE for newly created vm
Product: Red Hat Enterprise Virtualization Manager Reporter: Tareq Alayan <talayan>
Component: ovirt-engineAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, iheim, lpeer, michal.skrivanek, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Regression, Triaged
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-25 14:46:10 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
screenshot none

Description Tareq Alayan 2013-07-17 09:50:45 UTC
Created attachment 774709 [details]
screenshot

Description of problem:
Cannot set protocol to SPICE for newly created vm via UI

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

How reproducible:
always

Steps to Reproduce:
1. create a vm 
2. right click -> console 
3. protocle = SPICE

Actual results:
Failed updating the properties of the VM. This may be caused either by:
1. The values selected are not appropriate for the VM; or
2. Its values cannot be updated while the VM is in UP state (Please shut down the VM in order to modify properties such as CPU or cluster).

Expected results:
chenaged to SPICE 

Additional info:
screenshot attached

Comment 3 Michal Skrivanek 2013-07-25 14:46:10 UTC

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