Wanted to let everyone know about a recent change to the Manifests service on console.redhat.com that should be welcome for the Katello community 
Previously, if you managed Red Hat Enterprise Linux repos with Katello, it required either a Satellite manifest (which you can only create if you buy Satellite from Red Hat) or a “SAM” manifest, which was obsolete but the only way to get access to your RHEL subscriptions with upstream Katello.
With this change, live now, you can now create and download genuine Satellite manifests for import into Foreman/Katello. All that’s required is any valid RHEL subscription.
This allows you to generate a manifest at console-dot, import it, and then add subscriptions to it from the Foreman/Katello UI as needed. (For connected users) you no longer need to use the old access.redhat.com site.
(Air-gapped users will still need to use the old site to add subscriptions, for now.)
Details on permissions:
-
Any customer that wants to create, read, update, destroy (CRUD) a manifest on Hybrid Cloud Console needs to only have any active RHEL subscription.
-
Only users with subscription:manifest:write permissions (part of the Default Admin Access RBAC Role) can CRUD manifests.
11 Likes
I am actually very thankful to Red Hat for keeping this working, also for users outside of the Satellite use case
(aka. keeps working for orcharhino and Foreman)
And of course also thanks for keeping us updated on this topic!
2 Likes
That is great news.
An addition to the previous situation. The Satellite subscription can be added to a Red Hat account through the “Red Hat Developer Subscription for Teams” which includes Satellite (you need to be running test instances) and comes at no cost.
Downside: This subscription has to be obtained through the sales workflow (even though the cost is 0.0). This can take time to accomplish.
Well, I do not now if this is really working I still receive a message An active subscription that entitles you to use a supported on-premise application, such as Red Hat Satellite, is required for some features on this page. and can not attach any subscription to the manifest. Moreover I can not attach future dated subscriptions though it should work according the manual. The overall RedHat subscription system has always seemed to me overcomplicated.
Are you on access.redhat.com or console.redhat.com? The new changes would be on console.redhat.com. Also, note that it still requires a valid subscription for RHEL.
I am on console.redhat.com and I have a valid subscription for RHEL.
On console.redhat.com you cannot attach any subscriptions to manifests. This is by design and is a temporary situation - eventually manifests will not require subscription attachment at all.
Are you still able to create manifests as expected there?
Yes, and in its detail I can see 0 subscriptions. So when I import such a manifest into foreman I will be able to consume the subscriptions anyway ? Sorry for my ignorance, I can see it in your first announcement that it is possible via foreman to add subscriptions.
During the temporary situation I mentioned above, the flow is
- create a blank manifest on console dot
- import the empty manifest into Katello
- add subscriptions to it from the Katello web UI
Yes, I apologize, I have not read your announcement carefully
1 Like
So importing of the manifest now fails with Owner has already imported from another subscription management application. So maybe I have to cancel the original SAM ?
Yes, I think you’ll have to delete that manifest from Katello and then import.
Well, I deleted the manifest via hammer and imported the new one and everything seems to work fine, even the future dated subscriptions. Thank you for your help.
3 Likes