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.
[RFE] Applied Errata template in the RedHat Satellite, should generate errata report even if the erratas were applied manually by executing yum on the host or using a third-party tool
1. Proposed title of this feature request
Applied Errata template in the RedHat Satellite, should generate errata report even if the errata were applied manually by executing yum on the host or using a third-party tool.
2. What is the nature and description of the request?
Currently, the Applied Errata report populate data, only if the errata were pushed via satellite, as the report is generated by the auditing
the task(Actions::Katello::Host::Erratum::ApplicableErrataInstall), however when a customer applies errata manually on the hosts, then these tasks are
not generated in the satellite server, so the report does not populate any data.
3. Why does the customer need this? (List the business requirements here)
Customers can pull and verify the report for all hosts registered to the satellite server and identify whether a critical errata is applied on the hosts or not.
4. How would the customer like to achieve this? (List the functional requirements here)
In my opinion, by enhancing the combined profile task, so that the tasks should contain all the data for the hosts and
the report should be generated by auditing the combined profile tasks.
5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unknown
6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. satellite 7.0)?
No
7. Is the sales team involved in this request and do they have any additional input?
No
8. List any affected packages or components.
Unknown
This is simply not possible. We can't get the same information, namely the time of application, if it's not deployed from Satellite, since there's no way to get such data. We could get some information out of the package profile, but not all. That should become an new report though and would only give user a current snapshot of what's already applied on the host.
Forgive me, but "not possible" doesn't seem accurate to me.
In the past, it's been possible to extend yum via plugins so that its normal client operation can supply additional information to Satellite. Couldn't the same thing be done here?
Satellite already is (eventually) getting the info that errata that were showing as pending in Content->Content Hosts have been applied, and it's removing them from the pending errata there. Again, there's a lag on that operation, but it's happening.
Shouldn't it be possible to augment/extend yum to push (probably via POST) the necessary information to some endpoint on Satellite, to let it know "client X just applied <whatever> at <some time>".
Why is that "not possible" with current Satellite + yum or dnf?
I'm sorry I meant it's not possible to generate such report based on the data we currently have in the database. Of course there is a technical way how to get that data from hosts to the Satellite database, however that's very different and much more complex task, not just modifying the report itself.
Comment 12Dana Singleterry
2023-02-22 13:18:42 UTC
1. Proposed title of this feature request Applied Errata template in the RedHat Satellite, should generate errata report even if the errata were applied manually by executing yum on the host or using a third-party tool. 2. What is the nature and description of the request? Currently, the Applied Errata report populate data, only if the errata were pushed via satellite, as the report is generated by the auditing the task(Actions::Katello::Host::Erratum::ApplicableErrataInstall), however when a customer applies errata manually on the hosts, then these tasks are not generated in the satellite server, so the report does not populate any data. 3. Why does the customer need this? (List the business requirements here) Customers can pull and verify the report for all hosts registered to the satellite server and identify whether a critical errata is applied on the hosts or not. 4. How would the customer like to achieve this? (List the functional requirements here) In my opinion, by enhancing the combined profile task, so that the tasks should contain all the data for the hosts and the report should be generated by auditing the combined profile tasks. 5. Is there already an existing RFE upstream or in Red Hat Bugzilla? Unknown 6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. satellite 7.0)? No 7. Is the sales team involved in this request and do they have any additional input? No 8. List any affected packages or components. Unknown