-
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
Ledger writes not happening when an Endorser connection exists and issuer upgraded to 0.10.1 #2474
Comments
In the instance where this was discovered, we are finding that all attempts to create a RevReg are silently failing — the ledger transaction is not being written. As such, this may not be an issue with /rotate at all, and may just be an issue with this deployment. It had previously been able to create RevRegDefs before as needed... |
Based on the latest findings in the linked ticket, and the fact that everything was working fine before the upgrade, I'm skeptical this is just and issue with the deployment. |
Manually creating the RevRegDefs through the admin interface fails as well. |
@dbluhm has been able to tack down the issue; bcgov/DITP-DevOps#109 (comment) |
The updates contained in the 0.10.2-rc0 release fixed the reported issue and I was able to repair the agent's RevReg state. See the linked issue for details. |
When calling
/revocation/active-registry/{cred_def_id}/rotate
on existing, active RegRegistries, the existing registries are decommissioned but the new RevRegistries are not getting created.Scenario and details can be found here; bcgov/DITP-DevOps#109
The text was updated successfully, but these errors were encountered: