Comments

nimzie’s picture

nimzie CreditAttribution: nimzie commented

subscribing

tannerg’s picture

tannerg CreditAttribution: tannerg commented

subscribing

Perignon’s picture

Perignon CreditAttribution: Perignon commented
Status: Active » Postponed (maintainer needs more info)

New version of Storage API is being released right now. Can you re-confirm this as an issue?

So far I have not seen this happen but that does not mean this isn't true.

mdolnik’s picture

mdolnik CreditAttribution: mdolnik commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active

I can confirm this is still an issue in 7.x-1.8.

Same steps and scenario as above (except with Amazon S3 instead of DreamObject).

  1. Create new Storage Class and Amazon container
  2. Set the storage class's Amazon container to Propagate=Yes and Serve=Yes.
  3. Add the class to a node's file/image field.
  4. Upload files to node, save and run cron
  5. Everything works as intended (files moved to Amazon and links are updated).
  6. Set the Amazon container to External=Yes (OR set the class's container's Propagate to No).
  7. The existing files already on Amazon still work correctly.
  8. Any new files added to the field go to the initial container (Filesystem) as intended.
  9. When Cron is run, All the new files are physically deleted and cannot be recovered.

This seems to be an issue beyond the External setting as the same issue happens when there is only one class container and it's Propagate is turned off.

There should be a check to ensure that when deleting a file from a container, that it at least exists elsewhere (including the initial container)