Bug 28415
Summary: | rhn_register will register old RHL versions, but that isn't working well later | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Göran Uddeborg <goeran> |
Component: | rhn_register | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | 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-02-21 15:04:29 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
Göran Uddeborg
2001-02-20 12:35:46 UTC
This defect is considered MUST-FIX for Florence Release-Candidate #2 fisher wasn't supported by rhn_register; this was made clear in the release notes. We really don't have means of passing a better message back for invalid release and/or arch than what we are passing. About not being supported: The release notes said "rhn_register, the registration client for Red Hat Network, is included, but registrations for the beta will not be accepted." I interpreted that as meaning it would not be possible to register a machine as running release Fisher/7.0.90. Not that it wouldn't be possible to use the rhn_register enclosed to register older, supported, releases. Sorry if I misunderstood things. About the message: I wanted to suggest some way to stop this registration in an earlier stage. Either that rhn_register knew which releases are possible to register, or that the server side should refuse to accept registrations for unsupported/too old versions. Is this also infeasible? (Or maybe undesirable?) |