Open paul-butcher opened 8 months ago
None of these values are present in logs in January, so this must be new to 02-01
Actually, I've just searched again, and I have found them all, with the same error, on 2024-01-09. Evidently I set the date incorrectly when I first looked.
None of these b-numbers return any results from a search on the website (currently pointing to the 01-09 pipeline)
Apart from b31360051 (f5ndv2hu) these are all DELETED. I suspect the new pipeline is erroneously trying to create a full record for a DELETED one.
This remains a problem, but I don't think it's panic-worthy, and certainly not a blocker for deploying the 02-01 pipeline to the API.
They appear to be failing because they cannot find the corresponding data in storage. They all yield a message similar to this in the logs.
b20442117, b31360051, b24875831, b2170594x, b21705938, b24873342
They are all b-numbered (therefore goobi) METS files.
This has occurred in the new 02-01 pipeline, so may be due to recent changes to handle archivematica mets. This may be something that has been filtered out/guarded against before, but those changes have somehow removed that protection, or it may be something that happens in previous pipelines but has so far gone unnoticed.