Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSFS | Versioning | Concurrent delete latest & delete object by ID which is also the latest #8414

Open
romayalon opened this issue Sep 26, 2024 · 0 comments
Labels

Comments

@romayalon
Copy link
Contributor

Environment info

  • NooBaa Version: 4.18
  • Platform: All

Actual behavior

  1. During an effort of addition of concurrency tests (PR - NSFS | Versioning | Concurrency tests #8405), a test called concurrent delete objects by version id/latest is failing and currently being skipped, this test/scenario should be invesitigated and fixed.
    The failure is that we are not deleting the version and we just move it to .versions/.

Expected behavior

  1. A user creates one version of an object.
  2. After concurrent delete latest & delete object by ID which is also the latest NooBaa should create a delete marker and delete the existing version id.

Steps to reproduce

  1. Check the steps mentioned on concurrent delete objects by version id/latest.

More information - Screenshots / Logs / Other output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant