Description of problem: Based on support feedback a significant number of customers are attaching Satellite 6 or Satellite5->6 transition subscription to the Subscription Management Application when trying to generate Satellite 6 manifests. As a result, they don't see the subscription / SKU as available when actually registering the Satellite 6 server via subscription-manager and attaching subs. This is *unlike* Satellite 5 certificates where it's required to attach the Satellite subscription before being able to generate the cert. Proposed fix for Subscription Management Application of type Satellite, both new and existing, and for transferring subs between SMAs: 1) If the Satellite version is 5.x, clarify the message in attached screenshot satv5.png from "A Satellite certificate" to "A Satellite 5 certificate" to distinguish from Satellite 6. 2) If the Satellite version is 6.x, display a message in attached screenshot satv6.png to explain customers needs to attach the subscriptions to be managed by the Satellite 6 server, not the Satellite sub itself (**unless customer is doing a disconnected install and/or subscribing the Satellite 6 server to itself). Right now the "Download Manifest" is just grayed out with no messaging if no subs are attached so customer might be assuming it's the same reason as Satellite 5 above. 3) If the Satellite version is 6.x and customer attaches Satellite subscriptions, display messaging (mouse-over or text on UI) to explain that for Satellite 6, should not attach Satellite subs (including the transition sku) to the Subscription Management Application (**unless customer is doing a disconnected install and/or subscribing the Satellite 6 server to itself). Version-Release number of selected component (if applicable): current How reproducible: always Steps to Reproduce: 1. create or update Subscription Management Application of type Satellite v5 and 6 and compare 2. 3. Actual results: see above Expected results: see above (1-3) Additional info:
Created attachment 1024924 [details] satv5.png
Discussing further with BK, going to modify this request to just inform instead of disable, due to the user case where customers are creating disconnected distributors/manifests and/or subscribing the Satellite 6 server to itself: > 2) If the Satellite version is 6.x, display a message in attached screenshot > satv6.png to explain customers needs to attach the subscriptions to be > managed by the Satellite 6 server, not the Satellite sub itself (**unless customer is doing a disconnected install and/or subscribing the Satellite 6 server to itself). Right now > the "Download Manifest" is just grayed out with no messaging if no subs are > attached so customer might be assuming it's the same reason as Satellite 5 > above. > > 3) If the Satellite version is 6.x, disable attachment (gray out?) of > Satellite subscriptions and explain to the user (via mouse-over) that for > Satellite 6, should not attach Satellite subs (including the transition sku). > Instead of disable, display a text message that they do not need/want to attach Satellite sub to the Subscription Management Application to generate the manifest, unless the above. I defer to Sat 6 team/others for how to best word this...
This Bugzilla was originally opened on 2015-05-12, it's now 2017-08-07 and post-RHN UI shutdown, and Satellite 5 distributors no longer require Satellite subscription to be attached. So the revised messaging can be something like the following (paraphrased from https://access.redhat.com/articles/477863) : * Satellite 5 no longer requires attaching a Satellite subscription for the Satellite itself, only the subscriptions that will be consumed by the client systems managed by the Satellite server. * Satellite 6 does not require the Satellite subscription to be attached in order to generate the manifest. It is only used to register the Satellite with Red Hat Subscription Management in order to download the Satellite 6 packages.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days