Bug 487418

Summary: Default virtualization type for kickstart profile should not be Para-Virtualized host
Product: Red Hat Satellite 5 Reporter: Sayli Karmarkar <skarmark>
Component: ProvisioningAssignee: Partha Aji <paji>
Status: CLOSED CURRENTRELEASE QA Contact: Sayli Karmarkar <skarmark>
Severity: medium Docs Contact:
Priority: low    
Version: 530CC: cperry, duffy, jsefler, ssalevan, tsanders
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sat530 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 493749 (view as bug list) Environment:
Last Closed: 2009-09-10 19:24:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 457075    
Attachments:
Description Flags
mockup with first radio button selected
none
mockup with second radio button selected
none
mockup with third radio button selected none

Description Sayli Karmarkar 2009-02-25 21:27:05 UTC
Description of problem:
Current default virtualization type seems to be Para-Virtualized host when creating a kickstart profile which will install kernel-xen. 

It should be either "Xen Para Virtualized Guest" which does the work similar to "none" option that we used previously if we do not use it for virtual machine. This will require some additional note / documentation so that users clearly understand.
OR 
there should be one more "none" option in webui which should map to same "Xen Para Virtualized Guest". In this case no note/documentation is necessary.

Version-Release number of selected component (if applicable):
Satellite-5.3.0-RHEL5-re20090220.1-i386

How reproducible:
Create kickstart profile. 
Check virtualization options.
  
Actual results:
Para-Virtualized host as the default option. 

Expected results:
It should be either "Xen Para Virtualized Guest" with explanation note or "none".

Comment 1 Mike McCune 2009-02-25 21:28:57 UTC
Also need to add a NOTE: to the GUI explaining better what the type is used for:

NOTE: The virtualization type is used if you are using this Kickstart Profile to create virtual guests.  If you are not planning on using this Kickstart Profile for Virtualization you can just leave the selection at the default value.

NOTE: If you select Para-Virtualized Host RHN Satellite will automatically setup the machine to be ready to host Xen based virtual guests

Comment 2 Mike McCune 2009-02-25 21:30:24 UTC
Also, on the Details page for a profile we see KVM popping back in.

Need to filter that for Sat.

Comment 3 Sayli Karmarkar 2009-03-04 16:58:55 UTC
Máirín,

Can you take a look at bug description and suggest what seems to be the right thing to do in this case? 

~SayliK

Comment 4 Máirín Duffy 2009-03-04 20:01:11 UTC
Created attachment 334045 [details]
mockup with first radio button selected

Comment 5 Máirín Duffy 2009-03-04 20:02:29 UTC
Created attachment 334046 [details]
mockup with second radio button selected

Comment 6 Máirín Duffy 2009-03-04 20:03:54 UTC
Created attachment 334047 [details]
mockup with third radio button selected

Comment 8 Steve Salevan 2009-03-27 17:16:11 UTC
*** Bug 487772 has been marked as a duplicate of this bug. ***

Comment 9 Todd Sanders 2009-04-02 20:21:05 UTC
We need to keep any changes simple for v5.3 as we are way late in the cycle to make any significant ui changes.  Let's just add the "None" option, and propose the re-work for v5.4.

-Todd

Comment 12 Partha Aji 2009-04-22 17:41:58 UTC
moving to On_QA

Comment 14 Partha Aji 2009-05-20 14:23:45 UTC
Moving to ON_QA

Comment 15 Sayli Karmarkar 2009-05-22 20:07:56 UTC
verified.

Comment 16 John Sefler 2009-08-27 21:24:37 UTC
Verified on staged (Satellite-5.3.0-RHEL5-re20090724.0) with updates from Aug 20, 2009

The final Sat530 implementation is a dropdown with None as the default option...

Virtualization Type:
> None
> KVM Virtualized Guest
> Xen Virtualized Host
> Xen Para-Virtualized Guest
> Xen Fully-Virtualized Guest

moving to RELEASE_PENDING

Comment 17 Brandon Perkins 2009-09-10 19:24:24 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html