Azure Confidential Ledger ARM template re-deployment infinite loop calls to Ledger_ListBySubscription

Dev S 71

When using an ARM template to deploy an Azure Confidential ledger, resource of type Microsoft.ConfidentialLedger/ledgers, we see that the initial deployment of the Ledger runs fine, however, upon rerunning the ARM template, the deployment gets stuck with multiple calls to Ledger_ListBySubscription recorded in the Activity Log. There seems to be no end to the deployment and calls to Ledger_ListBySubscription keep getting logged every minute. The deployment gets stuck even when re-running the ARM template with 0 changes to the initial deployment.

Vinod Pittala 75 Reputation points Microsoft Vendor

2025-01-29T23:15:30.6533333+00:00
Hi Dev S

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

The issue you're encountering, where the deployment of Azure Confidential Ledger gets stuck and repeatedly logs calls to Ledger_ListBySubscription in the Activity Log, could be due to several factors.

Below are possible causes in detailed.

1st cause: When the first deployment of the Azure Confidential Ledger is successful, it creates the required resources. If there is any inconsistency in the state or configuration of the Ledger after the initial deployment (such as a partially completed resource), the ARM template may be repeatedly trying to validate or query the Ledger's state (which is what the Ledger_ListBySubscription API call represents).

Solution: Check the current state of the Ledger resource in the portal. Verify if it is healthy and fully deployed. If you find any inconsistencies or partial deployments, you may need to manually resolve or clean up the resources. It might also help to manually delete the existing resource and try redeploying the ARM template from scratch.

You can also check the activity logs or deployment history that may give more context about the ongoing job.

2nd cause: ARM templates are designed to be idempotent, meaning they should only change the resources if there are changes in the template. However, if the template has issues like incorrect conditions, parameters, or missing dependencies, it might be repeatedly trying to apply the same changes without detecting the existing resource.
Solution: Review your ARM template for potential issues like conditions or parameters that might cause it to continually attempt to apply changes. Pay attention to resource definitions that may be incorrectly marked for recreation or updating.

Below is the reference template that can provide you with further understanding.

https://learn.microsoft.com/en-us/azure/confidential-ledger/quickstart-template?tabs=azure-cli%2CCLI#review-the-template

3rd cause: The Ledger_ListBySubscription API calls are part of the Azure Confidential Ledger's resource provider. If the resource provider is not correctly registered or if permissions have changed, the template might repeatedly attempt to validate or list existing Ledger resources without success.
Solution: Ensure that the resource provider Microsoft.ConfidentialLedger is properly registered in your subscription.

Refer to the below document for your reference.

Create an Microsoft Azure confidential ledger by using Azure Resource Manager template | Microsoft Learn

You can check the status by running the following Azure CLI command:

az provider show --namespace "microsoft.ConfidentialLedger"

If it's not registered, register it with the below Azure CLI command:

az provider register --namespace "microsoft.ConfidentialLedger"

4th cause: Continuous calls to the Ledger_ListBySubscription API could indicate API throttling or rate limiting issues. If the deployment is hitting a rate limit or there is a high volume of requests being sent to the API, the deployment might get stuck in a loop.

Solution: Check for throttling errors or limits in the activity log. If necessary, you could add delay mechanisms or reduce the frequency of retries in the deployment script to prevent hitting the rate limits.

5th cause: If a previous deployment left behind a lock or an active resource that is preventing subsequent changes, the deployment could hang while trying to access the Ledger.

Solution: Check if there are any locks applied to the resource group or resource that could be preventing updates. Remove any unnecessary locks and try the deployment again.

By examining these alternatives, you should be able to identify the root cause of the issue and resolve the recurring deployment problem.

If the provided answer is helpful for you, please “upvote it”, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Thanks

Share via

Azure Confidential Ledger ARM template re-deployment infinite loop calls to Ledger_ListBySubscription

Your answer