no error is displayed if Transfer Source directories are empty or not readable
|Google Code Legacy ID:||Pull Request:|
If the dashboard is unable to read the contents of a selected Transfer Source directory, then the contents of a new Transfer will be empty (i.e. the objects directory will have nothing in it). An error should be shown at the Accept Transfer microservice. Instead, the transfer continues without error, but nothing is happening in any of the microservices. When it is time to create a SIP, no sip is created, because the checkTransferDirectory for objects microservice returns 0.
To reproduce, set up a pipeline that is using a remote storage service. Choose default storage locations, which creates storage locations that are local to the storage service, not local to the pipeline. In this scenario, it will be possible to browse the directory structure of the Transfer Source, but new transfers will get created without any objects in them.
#2 Updated by Misty De Meo over 8 years ago
This also occurs if individual files within a transfer have incorrect permissions. For example, I had a transfer which consisted of one file that was
rw------. The archivematica user didn't have permission to read it, so it proceeded with an empty transfer instead.