Description of problem: I'm using a combination of rhnreg_ks in a kickstart file and firstboot for a desktop deployment. firstboot nags my users to register even though they're already registered. Should be a pretty simple fix - just add a class similar to NoNetworkPage that checks rhnreg.registered(). Version-Release number of selected component (if applicable): RHEL 5.1, firstboot-1.4.27.3-1, rhn-client-tools-0.4.16-2.el5_1.9 How reproducible: Every time Steps to Reproduce: 1. Create a kickstart with a combination of: firstboot --enable and /usr/sbin/rhnreg_ks --activationkey=<key> in the %post section 2. Reboot. Actual results: Firstboot nags the user to register when they boot for the first time. Expected results: Firstboot should thank the user for registering with RHN. Additional info:
Created attachment 304988 [details] Possible fix This is a humble attempt at correcting the problem using the "skipme" attribute.
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 therefore 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-2009-1354.html