Description of problem:
Did a CSV export via the UI of the configuration management report page. Set the filter to "eventful=false".
2 reports were listed (see the attached screenshot).
When I did the CSV export the resulting file had entries for all reports, including ones that did not belong to the "Default Organization", event though I was in this context.
Version-Release number of selected component (if applicable): 6.3.0
How reproducible: Always
Steps to Reproduce:
1. Create a host, and cause a puppet report to be generated.
2. Click "Export" button to export to CSV
Actual results: All Reports included in exported CSV
Expected results: Only the reports that are visible via the filter.
Additional info: Attached resulting CSV and screen shot, as well as foreman-debug
Created attachment 1300029 [details]
Exported CSV of reports page
I did some additional testing on this an noticed that when there was no filter, it produces the full list of hosts.
It seems to be that the export is not taking into account the Organization/Location context when there in some cases when either:
1. There is no filter.
2. The filter is " eventful = false"
In these cases the CSV contains hosts that are not in the "Default Organization"
There could be other filters that trigger this as well.
Created attachment 1300070 [details]
It seems the filter field is respected, but the org/loc context isn't. Changing title accordingly and cloning to redmine.
Created redmine issue http://projects.theforeman.org/issues/20327 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20327 has been resolved.
Verified on sat 6.3 snap 13, the csv export from config management reports now honors both the filter and the present organization.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> For information on the advisory, and where to find the updated files, follow the link below.
> If the solution does not work for you, open a new bug report.