Bug 675342

Summary: Virtualization field on web UI is changed when re-registering a virtual machine using KVM
Product: Red Hat Satellite 5 Reporter: Marcelo Moreira de Mello <mmello>
Component: WebUIAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: mmello, slukasik, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-09 09:22:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 526735    
Bug Blocks: 462714    

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 ***