-
Notifications
You must be signed in to change notification settings - Fork 516
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
ACA-Py 0.10.1 and 0.10.2-rc0 - Errors when calling /revocation/registries/created and /revocation/registry/{rev_reg_id}/fix-revocation-entry-state #2485
Comments
I'll be testing with another set of agents that have been through an upgrade to |
Here are the results from testing on another agent. They indicate this issue may be isolated to the one agent. IDIM-dev agent upgraded from At
At
|
@shaangill025 — based on what the bug was, does this seem right? That running the command on 0.10.1 triggers a write that impacts future usage? |
The following error is being triggered when calling
This is because there is at least one
Solution: Implement a custom upgrade function to update such records and execute it with the |
This error is consistent with the issue that was previously identified with the LSBC |
Agreed upon solution that @shaangill025 will implement:
That will allow us to execute the process on a one-time basis on any environment that needs it. |
@shaangill025, Test results from #2486. Error log from a test run on the LSBC
|
Test results from the latest changes to #2486. Log from a test run on the LSBC dev agent. No errors this time.
cc @shaangill025, @esune, @swcurran |
The call to
However there is still an issue with some calls to
A call to
Where a call to
Error log: lsbc-0.11.0-pre1-pr2486.log There are RevRegEntries associated to both RevRegs:
|
RevReg(s) with associated errors from
lsbc-0.11.0-pre1-pr2486 - LedgerNotFound.log
|
The active CredDef is
The active registry is |
The error on the first revocation registry appears to be caused by an old tails server url that has long been gone: Unsure about the second issue... 🤔 |
Yes, the |
I've confirmed the registries associated with the This just leaves the error associated to the active RevReg, |
Testing updates for @shaangill025: Results from calls to
|
Based on discussions with @shaangill025 and @andrewwhitehead, the LSBC The calls to to
|
When trying to fix the state for
lsbc-0.11.0-pr2486-pre2 - error - fix-revocation-entry-state - apply.log RevReg Details:
|
Relevant backups of the LSBC
|
Testing of prerelease image
lsbc-0.11.0-pr2486-pre3 - revocation-entry-state - apply.log |
LSBC has confirmed their workflows, including revoke and reissue scripts, are working as expected in |
To clarify this issue appears to be specific to an agent that has been upgraded from
py36-1.16-1_1.0.0-rc0
to0.10.1
prior to upgrade to0.10.2-rc0
. The same error(s) occur in 0.10.1 and 0.10.2-rc0. An agent upgraded frompy36-1.16-1_1.0.0-rc0
straight to0.10.2-rc0
does not appear to be affected.Scenario:
dev
upgraded frompy36-1.16-1_1.0.0-rc0
to0.10.1
, and then to0.10.2-rc0
is having this issue.test
upgraded frompy36-1.16-1_1.0.0-rc0
to0.10.2-rc0
- the calls work as expected.lsbc-dev-0.10.1.log
lsbc-dev-0.10.2-rc0.log
The text was updated successfully, but these errors were encountered: