Closed WadeBarnes closed 1 year ago
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; https://github.com/bcgov/DITP-DevOps/issues/109#issuecomment-1710133517
Issue is specifically #2475 , and should be resolved by #2476 .
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; https://github.com/bcgov/DITP-DevOps/issues/109