Bug 675342 - Virtualization field on web UI is changed when re-registering a virtual machine using KVM
Summary: Virtualization field on web UI is changed when re-registering a virtual mach...
Keywords:
Status: CLOSED DUPLICATE of bug 526735
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 540
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 526735
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-02-04 23:33 UTC by Marcelo Moreira de Mello
Modified: 2011-06-14 12:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-09 09:22:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marcelo Moreira de Mello 2011-02-04 23:33:27 UTC 
Description of problem:
Virtualization field on web UI is changed when re-provisioning a virtual machine. 

Initially it shows 'Fully Virtualized' but when re-provisioning the same virtual guest, it changed to 'KVM/QEMU'

The Virtualization type = Fully Virtualized  is shown only while first time registering system.

Version-Release number of selected component (if applicable):
Red Hat Network Satellite 5.4


How reproducible:
100%


Steps to Reproduce:
1) Install a fresh RHEL 5 guest system on RHEL 5 KVM Host

2) Register that system, in system profile details we will see Virtualization type = Fully Virtualized 

3) Re-register system, in system profile details we will see Virtualization type = KVM/QEMU 

4) Even if we re-register system again then it will show KVM/QEMU only in system profile. 

Expected results:

 Understand why it shows 'Fully Virtualized' just for the just time
Comment 1 Marcelo Moreira de Mello 2011-02-04 23:35:25 UTC 
Small correction: 

  Expected results:

 Understand why it shows 'Fully Virtualized' just for the first time
Comment 3 Milan Zázrivec 2011-02-09 09:22:18 UTC 
This is the same problem as described in bug #526735

*** This bug has been marked as a duplicate of bug 526735 ***
Note You need to log in before you can comment on or make changes to this bug.