Bug 445881

Summary: firstboot is unaware of whether a system is already registered
Product: Red Hat Enterprise Linux 5 Reporter: Michael Solberg <msolberg>
Component: rhn-client-toolsAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.1CC: bperkins, cperry, jhutar, pkilambi, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 11:21:39 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:
Attachments:
Description Flags
Possible fix none

Description Michael Solberg 2008-05-09 15:52:12 UTC 
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:
Comment 1 Michael Solberg 2008-05-09 21:20:42 UTC 
Created attachment 304988 [details]
Possible fix

This is a humble attempt at correcting the problem using the "skipme"
attribute.
Comment 14 errata-xmlrpc 2009-09-02 11:21:39 UTC 
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