-
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
status: code = 1024 message = malformed request: token is invalid at NUMBER epoch #520
Labels
bug
Something isn't working
Comments
vvarg229
changed the title
Some tests are stopped during execution for a long time - more than 40 minutes
status: code = 1024 message = malformed request: token is invalid at NUMBER epoch
Mar 21, 2023
roman-khimov
added a commit
that referenced
this issue
Mar 21, 2023
This, btw, can be fixed in neofs-node master. IIRC there was a number of related changed relatively recently. |
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
May 5, 2023
This commit removes the @pytest.mark.skip and issue_* decorators that were temporarily skipping tests related to specific issues. The problems associated with these tests have been resolved in the neofs-node project, allowing them to be executed along with other tests. List of removed issues: nspcc-dev/neofs-node#2262 nspcc-dev#519 nspcc-dev#520 nspcc-dev#521 nspcc-dev#523 nspcc-dev#524 nspcc-dev#533 nspcc-dev#539 https://j.yadro.com/browse/OBJECT-628 But according to the results of test runs added issues, here is their list: nspcc-dev#535 nspcc-dev#537 nspcc-dev#542 nspcc-dev#544 nspcc-dev#558 nspcc-dev#559 Signed-off-by: Oleg Kulachenko <[email protected]>
Fixed: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tests fail with an error:
AssertionError: Regex pattern 'code = 4097.*message = expired session token' does not match "Command: neofs-cli --config /home/varg/work/neofs-testcases/wallet_config.yml object head --rpc-endpoint 's01.neofs.devenv:8080' --wallet '/home/varg/work/neofs-testcases/TemporaryDir/31074b7b-d8b6-4b34-9555-67c7a443099b.json' --cid 'Ee3UfhzgMLdtAVapPSGzsBiMKtWL3Kzg7ZqwsBK1ubnz' --oid 'EdPd4ffc48eJp4CSGFMXqmAGJR14oYTU2FLLmbahuDMB' --json --session '/home/varg/work/neofs-testcases/TemporaryDir/56efd9ad-8cbd-4ebe-9f6a-d1213feaed57'\nError:\nreturn code: 1\noutput: rpc error: read object header via client: status: code = 1024 message = malformed request: token is invalid at 41 epoch)\n".
Allure report:
token_is_invalid.zip
It looks like a bug in the neofs-node.
But more research is needed to move this issue to the neofs-node project.
The text was updated successfully, but these errors were encountered: