+++ This bug was initially created as a clone of Bug #494679 +++

--- Additional comment from jpazdziora on 2009-12-02 03:36:48 EDT ---

The WebUI shows the following:

https://satellite/network/systems/details/hardware.pxt?sid=1000017067

DMI Info
Vendor: 	RLX Technologies
System: 	SB 1200i 0A07 0A07
Product: 	  	
Bios: 	        RLX Technologies
                RLXBIOS: Recover -  
Asset Tag: 	(system: 10040912359)
Board: 	 

https://satellite/network/systems/details/hardware.pxt?sid=1000017087

DMI Info
Vendor: 	  	
System: 	 
Product: 	  	
Bios: 	 
                -  
Asset Tag: 	(chassis: 10040912359) (chassis: 0) (board: 10040912359) (system: 10040912359)
Board: 	SSCI 432

--- Additional comment from jpazdziora on 2009-12-02 03:44:42 EDT ---

The conclusion is:

Satellite version 5.3 correctly displays in the DMI Info section data stored in the database (= data which also shows up in the search results). Satellite 5.0.2 displays the system value from the asset fiels ("10040912359" in our case, "KBKKV49" in customer's case).

The rhn-client-tools version rhn-client-tools-0.4.13-1.el5 managed to submit the DMI Info in such a way that it's stored in the database alright (and in Satellite 5.3.0 case, displayed alright).

The newer rhn-client-tools-0.4.20-9.el5 seems not to submit the data properly, or submit it in a way the Satellite expects it.

--- Additional comment from jpazdziora on 2009-12-02 03:47:29 EDT ---

Thus, even if this bugzilla is primarily about Satellite-side issue of the data not being displayed properly (and for that, the resolution is to upgrade to latest Satellite version), I think I shall use this bugzilla to investigate the regression that we have in the client-side which does not seem to submit the information properly.

For the record, when I was upgrading rhn-client-tools to the latest version, the following packages were also upgraded / installed:

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Updating:
 rhn-client-tools        noarch     0.4.20-9.el5     rhel-i386-server-5  804 k
Installing for dependencies:
 gamin                   i386       0.1.7-8.el5      rhel-i386-server-5  118 k
 gamin-python            i386       0.1.7-8.el5      rhel-i386-server-5   56 k
 python-iniparse         noarch     0.2.3-4.el5      rhel-i386-server-5   34 k
Updating for dependencies:
 m2crypto                i386       0.16-6.el5.6     rhel-i386-server-5  490 k
 rhn-check               noarch     0.4.20-9.el5     rhel-i386-server-5   37 k
 rhn-setup               noarch     0.4.20-9.el5     rhel-i386-server-5  110 k
 rhnlib                  noarch     2.2.7-2.el5      rhel-i386-server-5   63 k
 yum                     noarch     3.2.22-20.el5    rhel-i386-server-5  997 k
 yum-metadata-parser     i386       1.1.2-3.el5      rhel-i386-server-5   25 k
 yum-rhn-plugin          noarch     0.5.4-13.el5     rhel-i386-server-5   56 k
 yum-updatesd            noarch     1:0.9-2.el5      rhel-i386-server-5   22 k

Transaction Summary
=============================================================================

--- Additional comment from jpazdziora on 2009-12-02 09:45:15 EDT ---

On fully updated RHEL 5.4 (and RHEL 5.3) the information on the WebUI content is:

DMI Info
Vendor: 	RLX Technologies 	
System: 	SB 1200i 0A07
Product: 	SB 1200i 	
Bios: 	RLX Technologies
        RLXBIOS: Recover - 04/10/2002
Asset Tag: 	(chassis: 10040912359) (chassis: 0) (board: 10040912359) (system: 10040912359)
Board: 	SSCI 432

Thus, the fact that we've seen no information on machine which had RHEL 5.0 with only upgraded rhn-client-tools (+ dependencies) is probably caused by some old hal or other package, not providing information to rhn-client-tools in a format in which rhn-client-tools expects it.

--- Additional comment from jpazdziora on 2009-12-02 10:44:29 EDT ---

If after upgrading to latest rhn-client-tools I also upgrade to latest hal

Updating:
 hal              i386        0.5.8.1-52.el5    rhel-i386-server-5  388 k
Updating for dependencies:
 pm-utils         i386        0.99.3-10.el5     rhel-i386-server-5  68 k

and I restart haldaemon, and I run rhn_register, the information on the hardware page is the same as from fully updated RHEL 5.4.

So, the change that we could do to ensure that we provide the latest information is to

Requires: hal >= 0.5.8.1-52

However, I'd like to point out that the original issue reported by the customer is not a client-side issue. It is Satellite server side problem, when the information is properly stored in the database but presented incorrectly on the web page. So any change that we will do in rhn-client-tools will not help the customer unless they upgrade to Satellite 5.3.