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

Locked object cannot be dropped via neofs-cli control drop-objects #2145

Closed
abereziny opened this issue Dec 8, 2022 · 0 comments · Fixed by #2160
Closed

Locked object cannot be dropped via neofs-cli control drop-objects #2145

abereziny opened this issue Dec 8, 2022 · 0 comments · Fixed by #2160
Assignees
Labels
bug Something isn't working U3 Regular

Comments

@abereziny
Copy link

abereziny commented Dec 8, 2022

Steps:

  1. Put object to container (Applies to both simple and complex objects)
  2. Lock this object
  3. Find nodes which physically contains the object
  4. ssh to the host of the node
  5. perform neofs-cli control drop-objects
/opt/dev-env/vendor/neofs-cli control drop-objects  -o B77fKtRkjDubuqXoQKF3dwsBXg9dBJC25MvNDGsYcY2C/5AAyMXTiDH9eC5RCKtgqdwW3enawkpfjoEud5J4yvsAG --endpoint <endpoint> --wallet /opt/dev-env/services/storage/wallet01.json --config /tmp/s01-config.yaml

Expected Behavior

Object should be marked for deletion

Current Behavior

2050 error meaning object is locked. Note the double rpc error

RC:
 1
STDOUT:

STDERR:
 rpc error: rpc error: code = Internal desc = status: code = 2050

Environment

Neofs Bundle v1.0.1-nb-20221208.1

Automation

https://github.com/nspcc-dev/neofs-testcases/blob/master/pytest_tests/testsuites/object/test_object_lock.py#L632

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working U3 Regular
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants