-
Notifications
You must be signed in to change notification settings - Fork 31
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
Trying to cancel an on going remote attesation crashes #1713
Comments
what does it mean not local? what is it important? |
It's not that is important just the way I managed to ran into the issue :/ |
so does the attestation-id need to exist? Is a problem that the attestation has already been cancelled? |
so you can't reproduce it locally? |
It would be nice if you could provide a full reproduction path, form |
It does need to exist, the attestation was still on going |
Did you try to cancel from another environment / CLI instance by any chance? |
I managed to reproduce it locally:
And the controlplane logs:
|
It makes sense, since the passphrase is generated from the workload token. We can read this in the code:
We should probably find a better way. But for sure, that error message should be more friendly. |
ok, that makes sense. The use of a different token was they key that was missing. We definitely need to handle this better but it's not that pressing. |
Yes, that's exactly what I was doing. I was wondering if I could cancel an ongoing attestation locally. My use case was the following: |
The way I could reproduce it was:
chainloop attestation reset --trigger cancellation --attestation-id
Example of the error:
The text was updated successfully, but these errors were encountered: