# TREE rel-eng/RHEL4-RC-re0107.0 # ARCH confirmed on i386, ppc, s390 # RHN xmlrpc.rhn.webqa.redhat.com I am presented with the error dialog when sending the hardware profile using the graphical up2date client. The error appears to be triggered by the code found in the ActivatePage::activatePageApply() (see rhnregGui.py:572). The error appears to be preventing RHN registration. However, closer inspection shows that the system is registered to the channel and I can query RHN using commands like: up2date --show-channels, up2date -l ... NOTE: rhn_register --nox works fine. This appears to only occur during the graphical registration process. The system_id's that have observed the failure are noted below: Arch System ID ===================== i386 - ID-1005179891 ppc - ID-1005179888 s390 - ID-1005179893
Created attachment 109574 [details] Screenshot
Can you send me the output of python /usr/share/rhn/up2date_client/hardware.py for some of those boxes?
The x86_64 system is currently being utilized for other testing ... but here are the results of the command noted in comment#2 for ppc and s390: http://people.redhat.com/jlaska/144704-ppc.txt http://people.redhat.com/jlaska/144704-s390.txt
hmm, can I get a shell on one of those boxes? My initial thought was that it was a server fault, but I can't find anything in the server traceback logs to indicate that.
I see what it is. It's a bug introduced in the fix for #142332. A change to make firstboot do the right things (not hang on no network), causes rhn_register to not initialize it's hardware list correctly. This bug should affect all arches. Should probably be a blocker of some sort, if theres such a thing at this point. up2date-4.4.6 should have a fix for this, but firstboot stuff needs to be verified.
Created attachment 109606 [details] included patch from previous version
Created attachment 109608 [details] up2date changes in the new package
Some additional notes. On an IA64, up2date-4.4.5-1 fails as decribed above when run as "up2date --register", but succeeds when run through firstboot.
firstboot works fines, `rhn_register` shows the error. The hardware profile does not get sent up. It can get sent later with `up2date --hardware` or a schedule hardware update action. System does get registered correctly, sans the hardware information (though, as a side effect, the user has to specify a profilename manually). user can proceed past the error.
4.4.7 has the fix (actually, 4.4.6, but whose counting)
*** Bug 149007 has been marked as a duplicate of this bug. ***
*** Bug 150200 has been marked as a duplicate of this bug. ***
Moving to PROD_READY, as up2date-4.4.8-1 resolves the issue.
PROD_READY-->RELEASE_PENDING
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 the 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/RHBA-2005-711.html