Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 663361

Summary: RHEL5.5+ guests on RHEL6 host consuming physical RHN entitlements
Product: Red Hat Enterprise Linux 5 Reporter: Sebastian Skracic <sskracic>
Component: rhn-client-toolsAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.5CC: acarter, gasmith, psubrama
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-15 16:18:29 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:

Description Sebastian Skracic 2010-12-15 14:48:51 UTC
The host is a pyhsical, fully up2date, RHEL6 box registered to RHN and entitled with Virtualization Platform, 64-bit with KVM enabled.

  The guest is stock RHEL5.5 32-bit.  The exactly same behavior is observed for fully up2date RHEL5 guests. 

Expected behavior:

  Upon registering to RHN, the guest enjoys the free ride on the host virt platform entitlement, allowing it to pull RHN content without consuming any of the system and base channel entitlements.

Actual behavior:

  Upon registering the guest on RHN, it consumes:

  * 1 system entitlement slot
  * physical channel entitlement slot(s)

  The system details page for the guest is showing that it's (incorrectly) recognized as a physical machine.

  The host system in question has rhn-virtualization* RPMs installed and the cronjob is working properly.  On the 'Virtualization' page of the host, the guest is listed, but not hyperlinked to the guest profile in RHN, meaning the UUID matching didn't work properly.

Comment 1 Sebastian Skracic 2010-12-15 14:52:02 UTC
The host RPM manifest excerpt:

[root@x3 rhn]# rpm -qa rhn\* | sort
rhn-check-1.0.0-39.el6.noarch
rhn-client-tools-1.0.0-39.el6.noarch
rhnlib-2.5.22-9.el6.noarch
rhnsd-4.9.3-2.el6.x86_64
rhn-setup-1.0.0-39.el6.noarch
rhn-virtualization-common-5.4.14-1.el6sat.noarch
rhn-virtualization-host-5.4.14-1.el6sat.noarch


The guest:

[root@bnw ~]# rpm -qa rhn\* | sort
rhn-check-0.4.20-33.el5_5.4
rhn-client-tools-0.4.20-33.el5_5.4
rhnlib-2.5.22-3.el5_5.1
rhnsd-4.7.0-5.el5
rhn-setup-0.4.20-33.el5_5.4
rhn-setup-gnome-0.4.20-33.el5_5.4

Comment 3 Stephen Herr 2010-12-15 15:24:17 UTC
The root problem is that get_virt_info() (in rhnreg.py) can not determine a UUID for this system. The client must be able to tell RHN that the system is a virtual guest in order for it to be able to consume either a Flex Guest or an inherited Virtualization entitlement.

Comment 4 Stephen Herr 2010-12-15 15:25:20 UTC
As clarification, I was talking about the guest in the comment above.

Comment 5 Sebastian Skracic 2010-12-15 15:43:07 UTC
'dmidecode' output on RHEL6 host:

# dmidecode 2.10
SMBIOS 2.4 present.
10 structures occupying 306 bytes.
Table at 0x1FFFFEC0.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: Seabios
        Version: 0.5.1
        Release Date: 01/01/2007
        Address: 0xE8000
        Runtime Size: 96 kB
        ROM Size: 64 kB
        Characteristics:
                BIOS characteristics not supported
                Targeted content distribution is supported
        BIOS Revision: 1.0

Handle 0x0100, DMI type 1, 27 bytes
System Information
        Manufacturer: Red Hat
        Product Name: KVM
        Version: RHEL 6.0.0 PC
        Serial Number: Not Specified
        UUID: 2819FBB4-14C4-14AF-76B0-57E9DCBF2CFC
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Red Hat Enterprise Linux

Comment 6 Sebastian Skracic 2010-12-15 15:43:52 UTC
Errr, the above is executed on the *guest* of the RHEL6 host.

Comment 7 Sebastian Skracic 2010-12-15 15:45:52 UTC
'dmidecode' output on the RHEL5.5 guest on the RHEL5.5 KVM host:

# dmidecode 2.10
SMBIOS 2.4 present.  
11 structures occupying 331 bytes.
Table at 0x000FBDAF.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: QEMU
        Version: QEMU
        Release Date: 01/01/2007
        Address: 0xE8000
        Runtime Size: 96 kB
        ROM Size: 64 kB
        Characteristics:
                BIOS characteristics not supported
                Targeted content distribution is supported
        BIOS Revision: 1.0

Handle 0x0100, DMI type 1, 27 bytes
System Information
        Manufacturer: Red Hat
        Product Name: KVM
        Version: Not Specified
        Serial Number: Not Specified
        UUID: D52D32C9-F8FF-F8B5-0323-B23A0192D103
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Red Hat Enterprise Linux

Comment 8 Stephen Herr 2010-12-15 16:01:54 UTC
It looks like I wrongly specified the UUID was missing. Actually it is the system.manufacturer. 

On the guest:
# python
Python 2.4.3 (#1, Nov  3 2010, 12:52:40) 
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import hardware
>>> data = hardware.get_smbios()
>>> data
{'smbios.system.serial': 'Not Specified', 'smbios.system.product': 'KVM', 'smbios.system.family': 'Red Hat Enterprise Linux', 'smbios.bios.vendor': 'Seabios', 'smbios.system.manufacturer': '', 'smbios.system.skunumber': 'Not Specified', 'smbios.system.version': 'RHEL 6.0.0 PC', 'smbios.system.uuid': '2819fbb4-14c4-14af-76b0-57e9dcbf2cfc'}

system.manufacturer is required to be "Red Hat", see 
https://bugzilla.redhat.com/show_bug.cgi?id=593317#c20
and 
https://engineering.redhat.com/trac/rhn-hosted/wiki/FloatingVirtEntitlements/ContainerSupport

Comment 9 Stephen Herr 2010-12-15 16:04:47 UTC
Also note comment 42 in the previous bug:
https://bugzilla.redhat.com/show_bug.cgi?id=593317#c42

I do not believe that bug should be closedcurrentrelease.

Comment 10 Milan Zázrivec 2010-12-15 16:18:29 UTC
It is correct that bug #593317 is closed -- it's reported against RHEL-6,
the problem described here is a problem in RHEL-5.5 rhn-client-tools.

We're aware of the problem described here -- it is tracked in bug #624780
and will be fixed in RHEL-5.6

I'm closing this bug as a duplicate of bug #624780, reopen if you disagree.

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