Error creating pool node

Question

I've converted my pool creation code from Microsoft.Azure.Batch to Azure.ResourceManager.Batch (in order to set the certificate in the key vault instead of in the batch account). The pool is being created with the expected node, and all configuration settings for both look the same as an existing pool created with the previous package (using Batch Explorer). However, the node shows "External ip" = "Error occured retrieving public IP Address". It also cannot get the "node agent version", has no files, and is stuck in the "Starting" state. I'm assuming these are all downstream from the IP problem.

I tried uploading logs but that erred out, again probably because it can't communicate.How would I diagnose this problem?

[FWIW, I can connect to a good node on the same subnet and see the bad node (arp -a) but it doesn't respond to pings. Assist said to run Test-NetConnection on the node management endpoint and that was fine.]

Thanks.

Answer 1

Hello Green, Jim

Thanks for sharing the requested details and your patience on this.

This issue is due to wrong configuration in the Azure Key Vault extension. Please refer this document: https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/key-vault-windows?tabs=version3#property-values

1.msiClientId under "authenticationSettings" shall be the "Client ID" (but not resource Id) of the UMI.

2.certificateStoreName shall be defined in the observedCertificates.

Please check the above details and also make sure the UMI has enough permission to access the key vault.

Hope this helps.

If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.