My team is using the Daml Contracts Upgrade tool version 2.5.5. We generated the upgrade project successfully and are testing it out in canton sandbox.
We’re now are now trying to test the upgrade process itself in canton sandbox, where we uploaded the proper dars and created a few contracts, 6 to be more specific. To achieve this we’ve consulted the provided documentation and are executing the necessary steps as described,
For the purpose of this test, we have two parties, system and cak. The system party has visibility over all templates. Sometimes either system and/or cak are signatories of some of the templates.
As I said, we are following the steps mentioned in the Daml Upgrade Tool documentation and it all goes well, and as expected (we launch and consult the navigator to see how the ledger changes along the way), until the run-upgrade command (Step 4: Execute the Contract Upgrade). We’ve tried different configurations but in our latest attempt the system party is solely the upgrader and upgradeCoordinator. Both parties are only used in Step 3’s command in order to give consent and accept contract upgrade proposals.
The problem is that contract template types that have the cak party as a signatory (individually or in combination with the system party) aren’t getting upgraded, and we are getting the error message presented below for these template types.
Even though we get a few of these error message the command keeps running indefinitely.
Would it be possible to get some assistance to understand if it’s some misconfiguration on our end, if we’re missing some step, etc.
Thank you in advance.
Best Regards,
João Palma Santos