Bug 172506

Summary: up2date File Not Found error after apparent downloading
Product: Red Hat Enterprise Linux 4 Reporter: Tim Johnston <tijohnst>
Component: up2dateAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED WONTFIX QA Contact: Ken Reilly <kreilly>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: tsanders
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: 2012-06-20 16:05:40 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:

Description Tim Johnston 2005-11-05 15:26:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; en) Opera 8.50

Description of problem:
(first-timer) Fresh install of RHEL WS4, and signed up for a new rhn account 
before realizing that our University license runs off satellite rhn. Ran up2date 
maybe once, but unable to access any updates without activating rhn account. Ran 
batch script to register with our satellite rhn, but any attempt to run up2date 
beyond that point resulted in File Not Found errors... even after I had 
apparently downloaded the files.

Version-Release number of selected component (if applicable):
up2date-4.4.50-4.src.rpm

How reproducible:
Always

Steps to Reproduce:
1.Install RHEL with no subscription number, register on RHN
2.Run batch script to access University's satellite rhn
3.run up2date
  

Actual Results:  File not found errors

Expected Results:  up2date should find updates and install

Additional info:

Comment 2 Jiri Pallich 2012-06-20 16:05:40 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.