Description of problem:
Assume a Content Host with some OpenSCAP policy applied. That config (what policy to check against) is puppet based. Removing the policy means puppet will remove the config from the system, such that it wont further report any compliance to Satellite. So far so good.
Unregistering a Content Host (from the host side) or removing the Content Host (from Satellite side) currently makes no change to the SCAP config on the client. Which means, the system - after its removal from Satellite - is still reporting to Satellite. Such reports are denied with 404 Host unknown error, causing the reports are buffered in foreman-proxy spool for re-send (currently due to bz1651143, they sit there forever). This behaviour is unwanted and redundant.
Any decomissioning of a system should be preceded by (an attempt of) removal SCAP config - one possible scenario is 1) remove SCAP policy from the system, 2) run puppet against it (to purge the config), 3) remove the system snippets from Satellite. But that is just an idea / proposal, of course.
Version-Release number of selected component (if applicable):
100% (I guess)
Steps to Reproduce:
1. Assign some OpenSCAP policy to a Content Host
2. Wait for some OpenSCAP reports from the Content Host
3. Unregister the Content Host by either way (sub-man unregister or via Satellite). Let the system running.
4. Monitor if the system will send some more SCAP reports.
4. SCAP reports are still being sent.
4. No or at most one SCAP report is sent from the system.
Created redmine issue https://projects.theforeman.org/issues/25763 from this bug
*** Bug 1699260 has been marked as a duplicate of this bug. ***
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.