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.

Bug 1932184

Summary:	[RFE] Make Content_host.csv export from Hosts > Content host available as a report template.
Product:	Red Hat Satellite	Reporter:	Prakash Ghadge <pghadge>
Component:	Reporting	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.8.0	CC:	ahumbe, dsinglet, jsherril, mhulan, sajha
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 00:45:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Prakash Ghadge 2021-02-24 07:52:41 UTC

1. Proposed title of this feature request

>>  [RFE] Make Content_host.csv export from Hosts > Content host available as a report template.
 

3. What is the nature and description of the request?

>> Make Content_host.csv export from Hosts > Content host available as a report template as it provides a succinct summary of applicable patches (bug fixes, security, and enhancements) for each host.


4. Why does the customer need this? (List the business requirements here)

>> This report should be available to the hammer tool from the CLI to be used for automated reports. This summary information is the exact information requested by InfoSec teams. The applicable errata provides very detailed information about the available patches that cu does not want.
 

5. How would the customer like to achieve this? (List the functional requirements here)

>> By making Content_host.csv export from Hosts > Content host available as a report template.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

>>

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

>> No
 

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

>> No

9. Is the sales team involved in this request and do they have any additional input?

>> No

10. List any affected packages or components.

>> Report Templates

11. Would the customer be able to assist in testing this functionality if implemented?

>> Yes

Comment 3 Justin Sherrill 2021-05-14 15:45:55 UTC

For this we could just add errata counts by type and applicable package counts to the existing 'Host - Registered Content Hosts' report. 

We'll also add Content view, Lifecycle Environment.

Should we remove the applicable errata ids list?

Comment 6 Brad Buckingham 2022-09-02 20:25:18 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 7 Brad Buckingham 2022-09-05 22:56:27 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 11 Eric Helms 2024-06-06 00:45:14 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.