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 1527227 - [RFE] add additional info to activation key subscription attachment page
Summary: [RFE] add additional info to activation key subscription attachment page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium with 2 votes
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-18 21:41 UTC by Chris Duryee
Modified: 2021-09-09 13:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-01 18:35:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1423505 0 high CLOSED [RFE] add a "any derived SKU" field to activation key subscription management 2023-09-15 00:01:20 UTC
Red Hat Issue Tracker SAT-5009 0 None None None 2021-09-09 13:01:07 UTC

Internal Links: 1423505

Description Chris Duryee 2017-12-18 21:41:57 UTC
Description of problem:

Users get confused occasionally about how autoattach and subscriptions work with activation keys. It is not as simple as it may seem. There are four options, each with a different behavior.

autoattach on + subs on AK: "When the system registers, Satellite will select the most applicable subscriptions from those attached to the activation key. The most applicable subs are based on a number of factors including the system's installed products."

autoattach off + subs on AK: "Satellite will attach every subscription on the activation key to the host when it registers."

autoattach on + no subs on AK: "The system will select from any available subscription when it registers, and will attempt to choose the best one given what's installed on the system. This may include a temporary subscription provided by the hypervisor."

autoattach off + no subs on AK: "No subscriptions will be applied to the system when it registers."

This info is best in table format, but I typed it out to avoid bugzilla reformatting. If possible, it would be good if the above info was expressed on the activation page subscriptions page. This would replace the existing info box.

I'm not a UI expert, but it may be useful to show either all of the options at once, or have some other way to show the entire table. That way users don't have to experiment by setting various options in the web UI to see all of the info text.

Also, the text above is not the exact verbiage, but we can come up with that once it's time for the final strings.

Version-Release number of selected component (if applicable): 6.3.0 beta

Comment 2 Rich Jerrido 2017-12-19 13:47:35 UTC
Additional content can be pulled from https://access.redhat.com/blogs/1169563/posts/2867891 .

Comment 3 Bryan Kearney 2019-07-02 18:01:57 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 4 Bryan Kearney 2019-08-01 18:35:15 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


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