Project: duracloud
Issue DURACLOUD-318: Bit Integrity Service: Incorrect report when item on list does not exist
From David Arjanik (Columbia) on 12/15 Was unable to successfully complete Use Case 4: Preservation Monitoring Test. Here's an excerpt from my notes regarding 2.c of the use case test plan: c. Service Test 1 i. Using the initial listing from Test0 above, create a new listing file with some MD5s altered some entire line items removed some new line items Arjanik: Done. Altered checksums of first three lines, deleted the next three lines, and added two lines at the end for files not in the DuraCloud instance. Uploaded to "admin" as usecase4-service-test-1.md5 ii. Run fixity service with this altered listing as input as in the previous test Arjanik: Reconfigured service to run against this new md5 file. Report ran successfully, generating files fingerprints-service-test-1.csv and integrity-report-service-test-1.csv (names I specified in the reconfiguration). iii. Verify that erroneous entries were identified in the generated report Arjanik: Downloaded fingerprints-service-test-1.csv and integrity-report-service-test-1.csv. Arjanik: Checked integrity-report-service-test-1.csv. This file is attached. Only one line of report data: | space-id | content-id | 0:admin/usecase4-service-test-1.md5 | 1:admin/fingerprints-service-test-1.csv | status | | Invalid manifest file: newspace | README.txt | Error: metadata is null | for: newspace/README.txt | Arjanik: Deleted the new md5 file and the generated report files for this service test from the "admin" space to try again. Reconfigured and re-deployed the service. Downloaded the results. Same results. Edited the md5 file and replaced fictitious space "newspace" with "usecase3". Deleted the old report files and re-deployed the service. Downloaded the reports. Renamed the integrity report to integrity-report-service-test-1-2nd-try.csv and attached. Results are basically the same as before. Opened the fingerprints file. The new lines were correctly identified as referring to files that didn't exist in DuraCloud. The six files that I've attached: PERFECT MATCH TEST usecase4.md5 - this is the input file listing correct space contents and correct md5 checksums fingerprints.csv - this is the md5 checksum file generated by the Bit Integrity Checker integrity-report.csv - this is the diff report generated by Bit Integrity Checker This test was successful. ERRORS TEST: - The checksums of the first three files in the list were changed - The next three files were removed from the list. - The last two lines refer to files that are not in our DuraCloud instance. fingerprints-12-15-2010.csv - this file appears to use incorrect formatting in the last two lines, the lines with files that don't exist in the instance. integrity-report-12-15-2010.csv - this is the malformed integrity report. Service Configuration: Service Mode: Verify the integrity of a list of items Get integrity information from...:	The storage provider Salt: empty Store: AMAZON_S3 (0) Space with input listing: admin Input listing name: usecase4-service-test-1.md5 Output space: admin Output listing name: fingerprints-12-15-2010.csv Output report name: integrity-report-12-15-2010.csv -------------------
Story points: 1