Hide Forgot
Description of problem: When a v7 test server is configured the save command should store a copy of the test results on the v7 test server. The v7 test server's web interface should provide a way to review results stored there from multiple SUT's organized by vendor, make, model, host and date.
Created attachment 515059 [details] patch for the save command to send results to server if configured.
Created attachment 515060 [details] patch for adding libary function to upload the results file to the v7 server
Created attachment 515061 [details] documentbase.py patch to remove pre-existing file when saving compressed results
Created attachment 515063 [details] index.html patch adding link to stored results
Created attachment 515064 [details] cgi to save results files on the server
Created attachment 515065 [details] cgi to list saved results files
Created attachment 515066 [details] patch to xslt cgi for processing saved/compressed results files by server path
Created attachment 515069 [details] xsl template patch for passing path information in templates
Committed above patches to R15. Some issues remain, moving back to assigned.
Committed to R17
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A new feature has been added in v7 1.4 that when a v7 test server is configured the `v7 save' command will store a copy of the test results on the v7 test server, also the v7 test server's web interface provides a way to review the results stored there from multiple SUT's organized by vendor, make, model, host and date. Typcially, the general results can be views with the following URL: http://<v7-server-hostname>/v7/ and detailed result for each SUT can be downloaded from the links in the page.
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. http://rhn.redhat.com/errata/RHBA-2011-1436.html