[BUG] [s3fs] files are not deleted

[dead10ck]

With s3fs, when a file is deleted from the bucket, is does not get deleted from the master or minion when they sync with s3.

This can cause strange and confusing results when files are deleted or moved. For example, if a state file is removed, but you forget to remove its invocation from top.sls, it still exists in the minion's / master's cache and will still apply the old state.

[OrangeDog]

Please provide all the information requested in the Bug template.

Can you confirm you have run salt-run fileserver.update but the deleted states still appear to be present?

[dead10ck]

None of the info I left out from the template is relevant. You can see for yourself in s3fs.py that it does not delete any files anywhere. I'm actually already in the process of developing a fix for this.

Can you confirm you have run salt-run fileserver.update but the deleted states still appear to be present?

As I said

is does not get deleted from the master or minion when they sync with s3.

This is exactly the bug I'm reporting.

[OrangeDog]

None of the info I left out from the template is relevant

In your opinion.

You haven't even said what version of Salt you are using.

[dead10ck]

Here's the commit history for s3fs.py. You'll notice the last one was two years ago. Tell me some more about the subjectivity of the version's relevance to this issue.