You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Second put_object_legal_hold with {"Status": "OFF"} results in 500:
2023-10-19T23:19:02.176Z error handler/util.go:29 call method {"status": 500, "request_id": "b58bf023-c37b-4c02-85c1-5baa25a9fa54", "method": "PutObjectLegalHold", "bucket": "yournamehere-q2bte72e99rpkueh-1", "object": "file1", "description": "couldn't head put legal hold", "error": "couldn't delete lock object 'CLdPcpKkxqLuyho2qiBYtDDSFW3x1WdTQ4pjyxW8wBHS' to remove legal hold: mark object removal via connection pool: status: code = 1024 message = incomplete object PUT by placement: could not close object stream: (*putsvc.remoteTarget) could not put object to [/dns4/s01.neofs.devenv/tcp/8080]: finish object stream: status: code = 1024 message = incomplete object PUT by placement: could not close object stream: could not delete objects from tombstone locally: lock object removal"}
If this action is not supported - then NotImplemented should be returned
The text was updated successfully, but these errors were encountered:
After some investigation and @carpawellhelp I should say, setting OFF with PutObjectLegalHold is not supported by the gate.
This was mentioned in docs but I consider It was not clear enough to understand. In PR #889, I've added a clean error and extended docs.
Second put_object_legal_hold with {"Status": "OFF"} results in 500:
If this action is not supported - then NotImplemented should be returned
The text was updated successfully, but these errors were encountered: