You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
Since 6.4 Satellite, we need "Red Hat Ansible Engine" product for installation from Employee SKU.
Earlier we could just use all the needed products from Red Hat Satellite Employee Subscription.
This issue is for working towards exploring to obtain 1 single subscription with all products required, probably ask around if "Red Hat Ansible Engine" product would be available in Red Hat Satellite Employee Subscription and get rid of Employee SKU.
Also, want to avoid being too dependent upon Employee SKU
Currently, the redhat-subscription role, needs two subs in the form of pool-ids.
The idea is, if we obtain a subscription with all required products in it, move to single pool-id.
The text was updated successfully, but these errors were encountered:
I think we can use Red Hat Satellite Infrastructure Subscription in this case as from my understanding it was designed to have all the products used by a typical satellite customer.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since 6.4 Satellite, we need "Red Hat Ansible Engine" product for installation from
Employee SKU
.Earlier we could just use all the needed products from
Red Hat Satellite Employee Subscription
.This issue is for working towards exploring to obtain 1 single subscription with all products required, probably ask around if "Red Hat Ansible Engine" product would be available in
Red Hat Satellite Employee Subscription
and get rid ofEmployee SKU
.Also, want to avoid being too dependent upon
Employee SKU
Currently, the
redhat-subscription
role, needs two subs in the form of pool-ids.The idea is, if we obtain a subscription with all required products in it, move to single pool-id.
The text was updated successfully, but these errors were encountered: