-
Notifications
You must be signed in to change notification settings - Fork 153
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
verifier fails with AttributeError: 'NoneType' object has no attribute 'checksum' #1306
Labels
Comments
This was referenced Feb 10, 2023
@mdrocco looks like one of the tests was accidentally disabled |
The fix seems simple enough, will take a look. |
Thanks, in fact that spot of the code has always been problematic with respect to my type-fixing adventure. Let me know if I can help somehow to fix this. |
maugustosilva
pushed a commit
to maugustosilva/keylime
that referenced
this issue
Feb 13, 2023
A bit of context: some runtime-policy tests were accidentally disabled (fixed by PR keylime#1307) were accidentally disabled. Once re-enabled they show a couple of bugs on the `verifier` and `tenant` code. This PR contains fixes for all these (basically need for checking for the presence of certain attributes/keys before referring to and use it) Signed-off-by: Marcio Silva <[email protected]>
@mdrocco submitted a bugfix |
maugustosilva
pushed a commit
to maugustosilva/keylime
that referenced
this issue
Feb 13, 2023
A bit of context: some runtime-policy tests were accidentally disabled (fixed by PR keylime#1307) were accidentally disabled. Once re-enabled they show a couple of bugs on the `verifier` and `tenant` code. This PR contains fixes for all these (basically need for checking for the presence of certain attributes/keys before referring to and use it) Signed-off-by: Marcio Silva <[email protected]>
maugustosilva
pushed a commit
to maugustosilva/keylime
that referenced
this issue
Feb 13, 2023
A bit of context: some runtime-policy tests were accidentally disabled (fixed by PR keylime#1307) were accidentally disabled. Once re-enabled they show a couple of bugs on the `verifier` and `tenant` code. This PR contains fixes for all these (basically need for checking for the presence of certain attributes/keys before referring to and use it) Signed-off-by: Marcio Silva <[email protected]>
mpeters
pushed a commit
that referenced
this issue
Feb 13, 2023
A bit of context: some runtime-policy tests were accidentally disabled (fixed by PR #1307) were accidentally disabled. Once re-enabled they show a couple of bugs on the `verifier` and `tenant` code. This PR contains fixes for all these (basically need for checking for the presence of certain attributes/keys before referring to and use it) Signed-off-by: Marcio Silva <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your issue a feature request? If so, please raise it as an enhancement
Environment
Description
keylime_verifier
fails to attest an agent and fails with the following errorThis is a regression introduced with #1272.
This bug has not been catched in CI, unfortunately the respective test has been accidentally disabled during the IMA policy overhaul update.
Expected behavior vs. actual behavior
verifier works properly and attests an agent
Steps to reproduce problem
Relevant logs
Logs from Rawhide are currently available at
https://artifacts.dev.testing-farm.io/2db622b2-5743-4765-b867-6c9094e9b098/work-upstream-keylime-tests-github-ci_zf645l9/plans/upstream-keylime-tests-github-ci/execute/data/functional/tenant-runtime-policy-sanity/data/
The text was updated successfully, but these errors were encountered: