Bug 445881 - firstboot is unaware of whether a system is already registered
firstboot is unaware of whether a system is already registered
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rhn-client-tools (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Pradeep Kilambi
Depends On:
  Show dependency treegraph
Reported: 2008-05-09 11:52 EDT by Michael Solberg
Modified: 2009-09-02 07:21 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-02 07:21:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Possible fix (11.70 KB, patch)
2008-05-09 17:20 EDT, Michael Solberg
no flags Details | Diff

  None (edit)
Description Michael Solberg 2008-05-09 11:52:12 EDT
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-, 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


/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 17:20:42 EDT
Created attachment 304988 [details]
Possible fix

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


Note You need to log in before you can comment on or make changes to this bug.