Bug 130637
Summary: | up2date shows traceback errors randomly | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Mohamed Eldesoky <mohamed.eldesoky> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | barryn, tim.nelson |
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: | 2004-09-05 07:42:30 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
Mohamed Eldesoky
2004-08-23 08:14:03 UTC
I upgraded to this version on 6 machines and got the same exact error. Downgrading to 4.2.16-1 and then upgrading to this version solved the problem. Strange? Here's how to fix it; I obviously don't have write access to the redhat source, so if Adrian could do this, that would be great. 1. Open /usr/share/rhn/up2date_client/repoBackends/yumRepo.py 2. Search for readHeaderBlob 3. Add a second parameter to the function call. The parameter name is remoteFilename 4. If your name is Adrian, release to the world NB: This fixed the problem for me. I don't pretend to understand the code, etc, but as soon as I turned the Fedora repo on, up2date would fail. As soon as I did this, I could do up2date cfengine, and that would come down from the Fedora repo. So it's better than nothing, anyway, and I'd like it if the fix were in the updates, so I wouldn't have to do this myself on our servers :). this should be fixed in rhel-u3 Why on rhel-u3 ?? Should we stop our work until rhel-u3 ?? It something that should be released in an errata !! Pumbing up priority and severity. Sorry, the error happened again. The only solution is to downgrade to a lower version. An urgent fix is required. We cannot wait till U3 is released. U3 is the next update for RHEL3. It will be available soon. |