Description of problem: Running submit twice back to back without any test runs or other changes to the results will upload to the catalog even though it is duplicate. Version-Release number of selected component (if applicable): v7-1.5-30 How reproducible: Everytime Steps to Reproduce: 1.run v7 and test something 2.run v7 submit, send to catalog but do not remove results 3.run v7 submit, send to catalog Actual results: v7 is allowed to upload the same results twice Expected results: catalog should return an error because the results are the same Additional info: This is a side effect of using gzip including the timestamp on results.xml as part of the submit. Passing the "-n" parameter to gzip will have it ignore the current time which results in the xml.gz package with the same test results content having the same md5sum.
Created attachment 588186 [details] documentbase patch adding -n to gzip
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: no tech note needed.
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-2012-0711.html