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

SPDK: accel_crypto_key_create: json response error: failed to create DEK, rc -22 #140

Closed
glimchb opened this issue Feb 9, 2023 · 0 comments · Fixed by #141
Closed

SPDK: accel_crypto_key_create: json response error: failed to create DEK, rc -22 #140

glimchb opened this issue Feb 9, 2023 · 0 comments · Fixed by #141

Comments

@glimchb
Copy link
Member

glimchb commented Feb 9, 2023

https://github.com/opiproject/opi-spdk-bridge/actions/runs/4134441153/jobs/7148943648
found the issue

spdk_1             | [2023-02-09 15:52:03.456606] accel_sw.c: 707:sw_accel_create_aes_xts: *ERROR*: key size 16 is not equal to key2 size 0 or is 0
@glimchb glimchb changed the title SPDK: 2023/02/09 15:52:03 DoFrontend tests failed with error: rpc error: code = Unknown desc = accel_crypto_key_create: json response error: failed to create DEK, rc -22 SPDK: accel_crypto_key_create: json response error: failed to create DEK, rc -22 Feb 9, 2023
glimchb added a commit that referenced this issue Feb 9, 2023
@glimchb glimchb linked a pull request Feb 9, 2023 that will close this issue
glimchb added a commit that referenced this issue Feb 9, 2023
Signed-off-by: Boris Glimcher <[email protected]>
Signed-off-by: Boris Glimcher <[email protected]>
glimchb added a commit that referenced this issue Feb 9, 2023
Signed-off-by: Boris Glimcher <[email protected]>
Signed-off-by: Boris Glimcher <[email protected]>
glimchb added a commit that referenced this issue Feb 9, 2023
Signed-off-by: Boris Glimcher <[email protected]>
Signed-off-by: Boris Glimcher <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant