Bug 112045

Summary: download of perl no valid GPG signature reported by up2date
Product: [Retired] Red Hat Network Reporter: Gavin C. Flower <gavin353>
Component: RHN/OtherAssignee: Mihai Ibanescu <mihai.ibanescu>
Status: CLOSED NOTABUG QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN StableCC: rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-23 21:10:10 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 dialog, date/time, etc.
none
2nd attempt: dialog, results of 'df', etc none

Description Gavin C. Flower 2003-12-13 16:20:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)
Gecko/20031210

Description of problem:
Used up2date to find components that could be updated on my Red Hat 9
system, selected Perl.  But download aborted with an error dialog.

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


How reproducible:
Always

Steps to Reproduce:
1.run up2date
2.select perl
3.download
    

Actual Results:  error

Expected Results:  perl updated

Additional info:

Comment 1 Gavin C. Flower 2003-12-13 16:23:47 UTC
Created attachment 96512 [details]
error dialog, date/time, etc.

Comment 2 Chip Turner 2003-12-15 13:23:35 UTC
this message can sometimes occur if you run out of diskspace (or are
low on disk space) in the /var partition.  Try removing
/var/spool/up2date/* and try again?

Comment 3 Gavin C. Flower 2003-12-15 16:19:54 UTC
Created attachment 96543 [details]
2nd attempt: dialog, results of 'df', etc

I deleted everything in /var/spool/up2date, but according to 'df' I had enough
disk space anyway.

Comment 4 Todd Warner 2005-09-23 21:10:10 UTC
2 year old bug. Assuming resolved.