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.
Description of problem:
The customer wants an erb report template for satellite future releases which will contain a number of packages available before and after the patching in the registered client machines.
Comment 1Waldirio M Pinheiro
2021-09-22 16:18:53 UTC
Hello,
Currently, there is a feature under console.redhat.com called Drift, which will do exactly what this customer is looking for. The customer can create a baseline with the current information, apply the patch and check/compare the status before and after installation.
I believe it to be a great workaround for now. Could you confirm that?
Thank you!
Waldirio
Could this be solved by providing the report template that gives "current" state of things for hosts? Customer would then run the report before the patching event and afterwards and compare. The reason is, we don't keep historical package profiles. Also I'd be curious if Waldirio's recommendation in comment 1 is acceptable, that sounds as a good solution to me. If not, please also specify the exact report columns you'd expect to see in such report.