Bug 75393 - up2dating a new package from RHN hangs
Summary: up2dating a new package from RHN hangs
Status: CLOSED DUPLICATE of bug 74726
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date   
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-08 01:36 UTC by Tom Wood
Modified: 2015-01-08 00:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-08 01:36:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tom Wood 2002-10-08 01:36:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Running up2date to fetch a previously uninstalled package hangs after download.

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

How reproducible:

Steps to Reproduce:
1.run "up2date packagename" (in my case, privoxy) from terminal window.
2.Watch package download.
3.Watch up2date prepare.
4.Watch up2date hang after 100% completion of install.
5.Watch RHN Alert Notification Tool turn from check mark to question mark.
6.Look on screen for popup window that states;
Error: <ProtocolError for www.rhns.redhat.com /APPLET: 502 Proxy Error>
7.Watch popup disappear when OK button pressed.
8.Watch RHN ANT turn back to check mark.
9.Be amazed that up2date still won't finish...
10.Be afraid that the rpm database is still locked...

Actual Results:  up2date didn't finish

Expected Results:  up2date should have finished

Additional info:

Comment 1 Tom Wood 2002-10-08 01:47:16 UTC
This looks to be the same problem detailed in bug 74726.  It does appear to be
an rpm problem, not necessarily an up2date issue.

*** This bug has been marked as a duplicate of 74726 ***

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