|Summary:||Managed Configs - Differences NOT Reported|
|Product:||Red Hat Satellite 5||Reporter:||Skip Paul <skpaul>|
|Component:||WebUI||Assignee:||Grant Gainey <ggainey>|
|Status:||CLOSED DEFERRED||QA Contact:||Red Hat Satellite QA List <satellite-qa-list>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-04-09 11:18:17 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Skip Paul 2014-07-01 17:28:29 UTC
Description of problem: Satellite has the capability to centrally manage configurations, and has a nightly job that runs to check if any of the configurations on the clients differ from those hosted on the Satellite. If you go into "schedule" in the satellite interface you can see a list of systems that ran the diff, however you have to click on each system to see if there are any differences. If you have ~500 systems registered to your satellite this is quite an arduous task. This method also does not produce a report. We have 'spacewalk-report system-history-configuration', however that only shows that a diff was run on a given system and doesn't show whether or not it returned any differences. The best option I've found so far is to go into systems tab, then click "systems" in the grey box, then "out of date". This shows a table of out of date systems and has a "configs" column which lists the number of configs which differ from the satellite-managed config. Unfortunately, when you click "download CSV" the "configs" column is not included in the report! Version-Release number of selected component (if applicable): I've verified this issue on 5.6, but I suspect it's also there in older releases. How reproducible: easily Steps to Reproduce: 1. configure client(s) to have centrally managed configurations through Satellite. 2. Modify the managed configuration file(s) locally, with a text editor, on the client(s). 3. Try to generate a report of non-compliant systems either through 'spacewalk-report system-history-configuration' or exporting a csv on the systems "out of date" page. Actual results: no systems with out of date configs are listed in the report/csv Expected results: A list of systems which have failed the difference check should be listed Additional info: This issue has been brought up by 2 of my customers who are under regulatory pressure to generate reports showing that centrally managed configs are "compliant".
Comment 2 Tomas Lestach 2018-04-09 11:18:17 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.