Open jrwdunham opened 6 years ago
This is a problem caused by the fact that the DIP generation/upload/store workflow splits from the AIP generation workflow. The inverse of this issue is that it is possible to successfully store a DIP without having stored an AIP, a situation that probably should not be allowed.
I think when an aip reingest is requested, if there are any un-answered user input questions (upload dip, store dip, store dip location, or any others) then the aip reingest request should fail, indicating that processing of the original aip is not complete.
I don't think this should be considered in scope for the 1.7.0 release - the workaround is to answer all user inputs before attempting aip reingest.
Steps to re-create
mv: cannot move ‘/var/archivematica/sharedDirectory/watchedDirectories/workFlowDecisions/metadataReminder/hierarchy_with_empty_dir_1508357212-9d46b1e1-af5b-4675-8cb3-acc177fddd15/DIP’ to ‘/var/archivematica/sharedDirectory/watchedDirectories/uploadDIP/hierarchy_with_empty_dir_1508357212-9d46b1e1-af5b-4675-8cb3-acc177fddd15/DIP’: Directory not empty
Presumably the unstored DIP created initially is still present and is causing this issue.