Bug 111632

Summary: rhnsd defaults to on for runlevels 3 4 5
Product: [Fedora] Fedora Reporter: William Hooper <redhat>
Component: up2dateAssignee: Bret McMillan <bretm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 1CC: mattdm, mitr
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-28 19:15:05 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:
Bug Depends On:    
Bug Blocks: 124619    

Description William Hooper 2003-12-07 04:54:35 UTC
Description of problem:
If updating a system that was previously registered with RHN rhnsd
causes errors:

[Sat Dec  6 11:55:58 2003] up2date Error communicating with server.
The message
was:
 
Error Message:
    Please run rhn_register (or up2date --register on Red Hat Linux 8.0)
as root on this client
Error Class Code: 9
Error Class Info: Invalid System Credentials.
Explanation:
[snip]

Since there is no RHN channel for Fedora shouldn't rhnsd be set to
"off" by default?  I see there is a check for
/etc/sysconfig/rhn/systemid which means new installs won't try to
check in, but it still might cause some confusion.


Version-Release number of selected component (if applicable):
up2date-4.1.16-1

Comment 1 Matthew Miller 2006-07-11 17:20:01 UTC
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.

Thanks!

NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.



Comment 2 John Thacker 2006-10-28 19:15:05 UTC
Closing per lack of response.  Note that FC1 and FC2 are no longer
supported even by Fedora Legacy.  Please install a still supported
version and retest.  If this still occurs on FC3 or FC4 and is a
security issue, please assign to that version and Fedora Legacy.

Note that up2date is not present in FC5 or FC6, the only current non-Legacy
Fedora Core releases.  However, related bugs may occur in yum, pirut, or other
updating mechanisms.