Bug 169659

Summary: firstboot fails on creating first user
Product: Red Hat Enterprise Linux 3 Reporter: Matthew Hauck <matt>
Component: firstbootAssignee: Chris Lumens <clumens>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-06-05 17:44:15 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
error message none

Description Matthew Hauck 2005-09-30 18:40:02 UTC 
Description of problem:
When I booted my RHEL 3 AS box for the first time, and it asked me to create a
user, it spit out an error and told me to file a bug.

Version-Release number of selected component (if applicable):
firstboot-1.1.19-1

How reproducible: firstboot only get's called once...
Comment 1 Matthew Hauck 2005-09-30 18:40:02 UTC 
Created attachment 119480 [details]
error message
Comment 2 Chris Lumens 2005-10-07 20:42:34 UTC 
What information did you provide on the user creation screen?
Comment 3 Matthew Hauck 2005-10-07 23:19:37 UTC 
"bigfix" for everything.
Comment 4 Matthew Hauck 2005-10-07 23:21:36 UTC 
but now as I think about it again...I think that firstboot might not have 
exactly run on its very first boot. So I think I already created the user 
with "useradd -p bigfix bigfix" or something of that sort.  This would 
probably cause firstboot to be confused.  So maybe this might be a bug related 
to firstboot's ability to run only on the first boot.
Comment 5 Chris Lumens 2005-10-11 16:08:57 UTC 
Do you remember how firstboot might have failed the first time through?  You can
have firstboot be run again on reboot if you:

# rm /etc/sysconfig/firstboot
# chkconfig firstboot on
Comment 6 Chris Lumens 2006-06-05 17:44:15 UTC 
Closing since I have been unable to reproduce this here and information has not
been supplied for several months.  Feel free to repoen this bug if you continue
to see this problem in a later update version of RHEL3.