computeDataFileHashValue returns success when datafile not present

What steps does it take to reproduce the issue?

call the computeDataFileHashValue API against a datafile which isn't present on storage.

• When does this issue occur?

when the datafile is missing

• Which page(s) does it occurs on?

the computeDataFileHashValue API endpoint

• What happens?

{"status":"OK","data":{"message":"Datafile rehashing complete. 86298 successfully rehashed. New hash value is: "}}

but server.log sez

edu.harvard.iq.dataverse.api.DownloadInstanceWriter
Datafile 86298: Failed to locate and/or open physical file. Error message: Failed to open local file file:///usr/local/dvn/data/10.5072/FK2/2WOH5X/17e264aecb9-daa13e53b966
edu.harvard.iq.dataverse.api.Admin
Unexpected Exception: Failed to open local file file:///usr/local/dvn/data/10.5072/FK2/2WOH5X/17e264aecb9-daa13e53b966

This happens on S3 as well.

• To whom does it occur (all users, curators, superusers)?

Must be a superuser to call computeDataFileHashValue

• What did you expect to happen?

A status of "not OK."

Which version of Dataverse are you using?

5.3, 5.9

Any related open or closed issues to this bug report?

no(?) but I bet Phil will know better.

Start by reproducing the issue through the computeDataFileHashValue API endpoint with a missing datafile, then compare its response with the related server.log errors from DownloadInstanceWriter and Admin. Done means a missing local or S3 datafile produces a not-OK status instead of reporting successful rehashing.