Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-5009

[RFE] add additional info to activation key subscription attachment page

XMLWordPrintable

      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

            jira-bugzilla-migration RH Bugzilla Integration
            jira-bugzilla-migration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: