Bug 985320 - Cannot set protocol to SPICE for newly created vm
Summary: Cannot set protocol to SPICE for newly created vm
Keywords:
Status: CLOSED DUPLICATE of bug 985260
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-17 09:50 UTC by Tareq Alayan
Modified: 2015-09-22 13:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-25 14:46:10 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (1.24 MB, image/png)
2013-07-17 09:50 UTC, Tareq Alayan 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.