Open LeoDeJaneiro opened 2 months ago
I traced the issue down to the lambda which cannot resolve the metadata file. I can confirm, that the *.metadata file does not exist for us for assets which have been uploaded with the 5.38.2 webiny version but for uploads with the updated version.
from the Logstream:
45fadc43-31dd-4f35-bedb-25058de88219 INFO Reading metadata 66263a76634da70008716c01/{filename}.png.metadata
2024-05-15T10:46:58.195Z 45fadc43-31dd-4f35-bedb-25058de88219 INFO S3AssetResolver failed to read metadata: The specified key does not exist.
Version
5.39.6
Operating System
all
Browser
all
What are the steps to reproduce this bug?
What is the expected behavior?
Assets should remain usable.
What do you see instead?
Assets are not found by Cloudfront: 404. The S3 bucket seems still filled, a random choice of assets shows that they are available there.
Additional information
I had a partly broken Webiny instance for some time due to the Node 16 Lambda runtime deprecation.
Possible solution
No response