Bug 114507 - proxy support for scrollkeeper-update
Summary: proxy support for scrollkeeper-update
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: scrollkeeper   
(Show other bugs)
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-28 20:56 UTC by Hans Deragon
Modified: 2007-04-18 17:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-06 22:23:42 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 Hans Deragon 2004-01-28 20:56:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

Description of problem:
Performing a kickstart upgrade from RHL 7.1 -> RHL 9, I notice that
the scrollkeeper-update script is called and attempts to download an
external DTD.  Like many enterprises, we are behind a firewall and
proxy and therefore, the attempt to fetch the DTD failed, as reported
by the scrollkeeper-udpate log:

xmlNanoHTTPConnectAttempt: Connect attempt timed
warning: failed to load external entity

It would be nice if we could provide proxy settings so that appication
requiring to fetch external data could do so.  Or better,
scrollkeeper-update should have all the DTDs available locally.

This is a serious problem because the timeouts last one minutes, but
scrollkeeper-update attempts many times to fetch DTDs (often the
same).  The result is that the installation seams to simply freeze
when it tries to upgrade a package.  I had to kill scrollkeeper-update
to get things going.

Version-Release number of selected component (if applicable):
Anaconda of RHL 9 boot CD.

How reproducible:

Steps to Reproduce:
1.Upgrade RHL 7.1 -> RHL 9 using kickstart


Actual Results:  scrollkeeper-update timeout.

Expected Results:  Faster upgrade.

Additional info:

Comment 1 Alexander Larsson 2004-02-09 11:23:54 UTC
It shouldn't need to get the DTD. It should be availible locally.
Might be a docbook setup issue.

Comment 2 Bill Nottingham 2006-08-05 04:17:17 UTC
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.

Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.

If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been

If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.

Comment 3 Hans Deragon 2006-08-06 22:23:42 UTC
I am not following this issue anymore.  I do not know if this still exist within
Fedora, as I do not perform anykind of upgrade with kickstart anymore.  I am
closing this bug report with CANTFIX.

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