Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Q1: Proposed title of this feature request?
Subscription report for disconnected Satellite with SCA
Q2: Who is the customer behind the request?
**See internal note**
Q3: What is the nature and description of this request?
RFE
Q4: Why does the customer need this?
The customer has a disconnected satellite deployment with SCA and requires tools to monitor subscription consumption in a disconnected environment. The customer cannot use extant subscription monitoring tools under SCA due to security implications (i.e. the Satellite Inventory Plugin and uploading inventory data to Subscription Watch on the Red Hat Hybrid Cloud Console).
The foreman-rake script described in Red Hat Solutions article 5414471 only provides minimal subscription data, such as: whether a host is subscribed or not, or whether SCA is enabled or not. The customer requires granular subscription consumption data that links an individual host to a specific RHEL product; data which the aforementioned foreman-rake script does not provide. For example, the customer would like to know exactly the quantity of hosts consuming the "RHEL Workstation, Premium" product at any given time, or the quantity of hosts consuming the "RHEL for Virtual Datacenters with Satellite, Premium" product at any given time.
Before enabling SCA earlier this year, the customer would monitor subscription consumption on the Subscriptions page on the Satellite web interface. This feature fulfilled the customer's subscription monitoring requirements at the time. However since enabling SCA, the customer can no longer use this feature to accurately monitor subscription consumption. Reverting to the old method of manually attaching subscription entitlements to individual hosts in order to use this Satellite feature is not a feasible option for the customer.
Considering the lack of appropriate SCA tooling to monitor subscription consumption for customers in high-security, disconnected environments, the customer would like to raise an RFE to introduce an "on-premises" SCA tool that allows customers to monitor their subscription consumption in a disconnected/air-gapped environment.
Q5: How would the customer like to achieve this?
Ideally, the Subscriptions page on the Satellite web interface is enhanced to show subscription consumption data with SCA enabled. The information that is already provided in the subscriptions table is what the customer requires - it just needs to show accurate consumption data under SCA.
Q6: For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented?
The Subscriptions page on the Satellite web interface displays consumption data that matches the number of hosts at the customer's site.
Q7: Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
Q8: Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
The customer is not under any specific timeline dependencies, however it is preferable for this feature to be introduced in a Satellite release sooner than later.
Q9: Is the sales team involved in this request and do they have any additional input?
No
Q10: List any affected packages or components
Satellite 6
Subscription Watch
Simple Content Access
Q11: Would the customer be able to assist in testing this functionality if implemented?
Yes