Description of problem: Impossible to download a CSV file of a probe event log. Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL4-re20090612.0 How reproducible: often, but not always Steps to Reproduce: 1. Enable monitoring on both sat. Install httpd on the client and start the service. 2. create a General: TCP Check probe for the client and set following probe params: Send: "GET\n" Expect: "buuuu" Port: 80 3. Push Scout 4. You can generate some data into the event log by stopping and starting httpd multiple times on the client. Check that by "Generate report" with checked "Show event log" 5. When there are some rows in the Event log on the probe page, try to "Download CSV" of the Event log. Actual results: You're redirected to the "Internal Server Error" without getting any CSV file. Expected results: CSV file without any problem.
Created attachment 348439 [details] Exception from the traceback
We were unable to diagnose just what was happening with this tag but this was using the older version of our list tag and using an extremely rare method for the CSV link, so Partha spent a few minutes switching it to the new list tag which does not have this problem. spacewalk.git: b9384a103a7e51afe3a2e524172280b3f37dae3f satellite.git: 7c3849809897007a5caaf9f7de59ef91653e6fac
Moving to ON_QA
verified .. looks good
Following a test plan from #Description ... getting a regular event csv file. Works! Stage validated -> RELEASE_PENDING
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html