Bug 50954
Summary: | Non-intutive error message | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Peter Bowen <pzbowen+rhbeta> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | CC: | m.a.young, srevivo |
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: | 2001-08-16 16:54:45 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
Peter Bowen
2001-08-05 16:59:55 UTC
We (Red Hat) should try to fix this for the next release. I had the same problem. I tried various things, but I think the problem was /etc/sysconfig/rhn/up2date still had an entry pointing at the main rhn server, not the beta one. I replaced this with the up2date.rpmnew file and reapplied my customizations, and the update now seems to get much further - it times out while trying to get the patch list. (An up2date -p may also be necessary after the change). I should have mentioned my upgrade was from seawolf to roswell. Assigned to the owner of component This is an artificate of the beta period. The new client uses a new server api, that the current www.rhns.redhat.com servers dont support. Since this was an update, your up2date config is still pointing at these new servers instead of at beta.rhns.redhat.com, which does support this new server function. Easiest thing to do is probabaly to copy over the .rpmnew files for /etc/sysconfig/rhn/{up2date,rhn_register} The live servers will soon support this new api as well. I didn't mean this bug to be about the exact error message, but the fact that up2date was throwing crypting errors in general. It should present the user with a more user friendly error message, with a suggestion for a possible fix, or someone to contact for more info. the next version of the client does (it catches this xmlrpc fault and presents a error dialog explaining how to fix it). I can't get the client to throw this error anymore. Closing out this issue then. |