Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 669467 - [RFE] Relation between Contract/Subscription number and Server ID - Satellite Client - and Expiration Date
Summary: [RFE] Relation between Contract/Subscription number and Server ID - Satellite...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sat-nextgen
TreeView+ depends on / blocked
 
Reported: 2011-01-13 18:28 UTC by Frederic Hornain
Modified: 2019-09-26 13:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-04 17:08:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Frederic Hornain 2011-01-13 18:28:31 UTC 
Description of problem:

Many customers would be interested to have the possibility to reply to that question :

What server is using what subscription ?

Ok, the workaround will be to create Activation Key for each contract number and to do regular check on the Red Hat customer portal to see expiration date.

But, it is adding another huge administrative task to our clients. 
And indeed they do not want that even if it is going to be more and more necessary. Specially when you start to play with hundred and hundred Red Hat Network Satellite Clients.

So, Could you help us to solve this huge and painful management problem ?

The first and the quicker reply to that problem will be to offer APIs on the Red Hat customer portal to our clients in order to let customers - in the case where they uses Activation Key ID with the contract number - the possibility to make the relation via scripts between contract number and activation Key.  

The second will be to create that relation in a transparent way for the customer in the RHNS.

It certainly exists other solutions, I let you imagination and innovation do their job ;).

Thanks in advance for your comprehension and you great help. 

BR
Frederic ; )
Comment 1 Clifford Perry 2011-01-19 22:26:52 UTC 
Hi,
Please open a support ticket for this RFE request. This will allow Red Hat to
help fill out an RFE template and align for Product Management review for future alignment. 

Regards,
Cliff
Comment 4 Bryan Kearney 2014-12-04 17:08:55 UTC 
In satellite 6.0, we support subscriptions which know their contract number. You can drill down into the systems which consume those subscriptions, and you can view the contract and order information from the system. We believe this meets the  requirements of this RFE. If you disagree, please feel free to re-open.

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