aries-cloudagent-python: 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

To clarify this issue appears to be specific to an agent that has been upgraded from py36-1.16-1_1.0.0-rc0 to 0.10.1 prior to upgrade to 0.10.2-rc0. The same error(s) occur in 0.10.1 and 0.10.2-rc0. An agent upgraded from py36-1.16-1_1.0.0-rc0 straight to 0.10.2-rc0 does not appear to be affected.

Scenario:

LSBC issuer in dev upgraded from py36-1.16-1_1.0.0-rc0 to 0.10.1, and then to 0.10.2-rc0 is having this issue.
LSBC issuer in test upgraded from py36-1.16-1_1.0.0-rc0 to 0.10.2-rc0 - the calls work as expected.

lsbc-dev-0.10.1.log lsbc-dev-0.10.2-rc0.log

About this issue

Original URL
State: closed
Created 10 months ago
Comments: 20 (20 by maintainers)

Most upvoted comments

I’ve confirmed the registries associated with the LedgerNotFound error either don’t exist or have an invalid tails server URL. Comments above have been updated with the details. I’d say we can safely ignore the error.

This just leaves the error associated to the active RevReg, UUHA3oknprvKrpa7a6sncK:4:UUHA3oknprvKrpa7a6sncK:3:CL:209518:default:CL_ACCUM:c6f98707-dbca-4ecc-92d6-5eb0837f20dc, that needs to be investigated.

WadeBarnes on Sep 15, 2023

Agreed upon solution that @shaangill025 will implement:

Create a “named” upgrade script for the specific issue identified here.
Add a feature that allows the “acapy upgrade” function to invoke a specific named upgrade script and execute that process.

That will allow us to execute the process on a one-time basis on any environment that needs it.

swcurran on Sep 8, 2023