Bug 68279 - up2date somehow gets bogus values for proxyAuth and tracebacks
up2date somehow gets bogus values for proxyAuth and tracebacks
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Depends On:
  Show dependency treegraph
Reported: 2002-07-08 16:23 EDT by Adrian Likins
Modified: 2007-04-18 12:43 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-20 22:35:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adrian Likins 2002-07-08 16:23:30 EDT
There seems to be an issue with proxy config information not
getting migrated properly from rhn_register.

Symptons seem to be that up2date  ends up with
up2dateProxyAuth enabled, but no ProxyUser or ProxyPasswd
set, eventually causing a traceback.

1) the code that uses these values should verify sanity

2) not sure yet how these bogus values got set, but the
code that migrates the proxy settings from rhn_register
look most suspicious.
Comment 1 Adrian Likins 2003-01-20 22:10:08 EST
no longer applicable with current code base.

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