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

Bug 985896

Summary: [Admin Portal] New VMs have VNC console by default, inheriting from Blank template VNC console type
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
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, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-18 14:53:52 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:

Description Jiri Belka 2013-07-18 13:08:39 UTC
Description of problem:

In clean installation of is6, new VMs inherit console type by default from Blank template. But Blank template got VNC console type now, this is regression from previous versions...

* upgrade from is5 to is6:

# psql -U engine -c "select vm_name,default_display_type from vm_static where vm_name = 'Blank';"
Password for user engine: 
 vm_name | default_display_type 
---------+----------------------
 Blank   |                    1
(1 row)


* clean install:

engine=> select vm_name,default_display_type from vm_static where vm_name = 'Blank';
 vm_name | default_display_type 
---------+----------------------
 Blank   |                    0
(1 row)


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

How reproducible:
100%

Steps to Reproduce:
1. have clean is6, create new vm
2.
3.

Actual results:
VNC console by default

Expected results:
SPICE as usual

Additional info:

Comment 1 Itamar Heim 2013-07-18 14:53:52 UTC

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