Bug 202986
Summary: | [RFE] Association between systems in the system list and their subscription contract | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | Alex Wood <awood> |
Component: | RHN/Web Site | Assignee: | rhn-dev-list |
Status: | CLOSED EOL | QA Contact: | Red Hat Network Quality Assurance <rhn-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhn521 | CC: | acarter, bughunt, msuchy, rhn-bugs, rmk |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-05 15:07:48 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
Alex Wood
2006-08-17 17:21:20 UTC
I second the motion with four thumbs up. I'm about to go postal over this. Explicit contract management is the way to go. Activition should not be more than ___these three manual steps____ 1) Buy a license key 2) Activate license key (at an easy-to-find place too, pretty pretty please, like a prominent place in the RHN site, NOT somewhere on www.redhat.com) Activation feeds a pool of contract numbers. You MUST be able to examine the association "license-key <--> contract number". And see the date of "license key entry". 3) Assign a contract from the pool to a system. You MUST be able to examine the association "license-key <--> contract number <--> system". And see the date of "license key entry", "contract assignment", "contract expiration". The current RHN is a management mess, sorry to say so. I can't even check whether what the RHN says is correct; it definitely is inconsistent with my notes I took separately. How do I explain this to bossman? User bnackash's account has been closed As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request. You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management). If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support). As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request. You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management). If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support). |