-
Notifications
You must be signed in to change notification settings - Fork 18
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
Enable Ceph tests for Object Lock #406
Comments
Ceph object lock tests enabled in gateway-st , not main, currently failing. Further review is needed. |
Report of failing tests and review of tests enabled underway. |
Change testsuite/ceph: Enable OL tests for partial implementation of Object Lock mentions this issue. |
We're only able to pass one addtional ceph test, |
bummer. but makes sense - we have initial validation from manual tests and associated integration tests... |
We initially used this ticket to test our early version of object lock that we used to validate Veeam compatibility. We are updating the ticket to include enabling ceph tests for our now complete version of object lock. |
Change miniogw: fix legal hold not implemented on single-tenant gateway mentions this issue. |
Updates storj/edge#406 Change-Id: Id1e56042abcf7c4155e7de5d2b286ff11113f55b
Change testsuite/ceph-s3-tests: re-enable more object lock tests mentions this issue. |
https://review.dev.storj.io/c/storj/gateway/+/15402 enables the rest of the object lock tests. I created a few new issues from the tests that are still failing:
These don't appear to be major problems. |
Goal
This issue is to make meaningful progress on Object Lock implementation within core and edge services. Specifically, to support immutable backups in backup software products like Veeam.
What needs to be done? • Acceptance Criteria
Let's find tests in test suites that we use that can be enabled for what we already implemented.
Depends on…
At least #397.
Links
The text was updated successfully, but these errors were encountered: