Bug 190551 - Registration error on First Boot
Summary: Registration error on First Boot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Ken Reilly
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-03 14:49 UTC by Kevin Pair
Modified: 2012-06-20 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:33:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
First boot error log ? (1.88 KB, text/plain)
2006-05-03 14:49 UTC, Kevin Pair
no flags Details

Description Kevin Pair 2006-05-03 14:49:19 UTC
Description of problem: fails to register for updates 
 
 
Version-Release number of selected component (if applicable):4.3 
 
 
How reproducible: have rebuilt that box twice 
 
 
Steps to Reproduce:  
1. Install OS 
2. First Boot 
3. Enter Registration info 
4. Fails to register 
   
Actual results: 
 
Shit don't work. 
 
 
Expected results: 
 
Shit to work. 
 
Additional info: Install disks worked fine on two other boxes.  The server 
seems fine except I can't get updates.

Comment 1 Kevin Pair 2006-05-03 14:49:19 UTC
Created attachment 128536 [details]
First boot error log ?

Comment 2 Bret McMillan 2006-05-03 16:17:44 UTC
Is your system time correct?  SSL can fail if clockskew is too great...

Comment 4 Red Hat Bugzilla 2007-04-12 00:39:48 UTC
User bnackash's account has been closed

Comment 6 Jiri Pallich 2012-06-20 13:33:02 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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