Description of problem: As a Satellite 6 user, I want to manage my Red Hat subscriptions from the Satellite instead of from the customer portal. I should have both options (the current way), or without needed to use the customer portal. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. log into the customer portal 2. create a manifest 3. add subscriptions 4. go to the satellite webui 5. upload the satellite manifest In addition if you need more subscriptions you now must go back to the customer portal and add subscriptions. Then back to the satellite webui to refresh (or use hammer on the command line for refresh). Expected results: We need a seamless way to manage subscriptions within Satellite, so you do not have to go back and forth from the customer portal.
*** Bug 1269233 has been marked as a duplicate of this bug. ***
Closed out older one from 2015 since it's more sparse with no case/kbases attached: Bug 1269233 - [RFE] ability to add or remove subscriptions to/from manifest from within Satellite 6 web UI There's also another related Bug 1216228 [RFE] Automate the process of generating manifests in Satellite 6
I wonder if this is something we can sneak in earlier, with a better fix for the 6.4 release?
In Satellite 6.4, the user will continue to create their manifest using the customer portal and import/upload in to Satellite. After that, they may choose to modify the content of their manifest (e.g. add, remove or modify) from within the Satellite UI.
(In reply to Brad Buckingham from comment #5) > In Satellite 6.4, the user will continue to create their manifest using the > customer portal and import/upload in to Satellite. After that, they may > choose to modify the content of their manifest (e.g. add, remove or modify) > from within the Satellite UI. Does it means there will be no Manifest "Refresh" required after the initial Manifest Import? If so, will there be a kind of Synchronization between what we see in Satellite vs the Portal? Thanks!
Manifest refresh will only be necessary if users change their subscriptions from access.redhat.com. An automatic manifest refresh is triggered when users modify subscription allocations from within Satellite.
What is the end step here? What is changed/added in 6.4 to verify this bug? Basically I am looking for steps to verify this bug.
This entire API was added as a result of this BZ: https://theforeman.org/plugins/katello/3.7/api/apidoc/v2/upstream_subscriptions.html Some acceptance criteria can be found on the upstream issues. The one linked is a tracker (http://projects.theforeman.org/issues/22595) to the many others which have more detailed information (only the features have acceptance criteria). For example, http://projects.theforeman.org/issues/22594 covers listing available subscriptions only (the GET endpoint in the API) and includes acceptance criteria.
Verified in Satellite 6.4 snap 22. Satellite has introduced this feature in 6.4. Users can now edit entitlement count, as well as add new subscriptions to their satellite, when linked to the portal. Additionally, users can also delete subscriptions they no longer want. See documentation for further details.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927