Since updating to App Layering 2603 we've been hav...
# citrix-app-layeringk
Keith Perri
05/27/2026, 4:20 PMSince updating to App Layering 2603 we've been having issues with the ELM not cleaning up Azure App Layering build VMs after a successful capture. The error on the Azure side when it tries to delete the VM is NoRegisteredProviderFound: "No registered resource provider found for location 'eastus' and API version '2026-03-01' for type 'virtualMachines'." Any ideas?
t
Tyler Benoit
05/27/2026, 4:24 PMYou are running into an issue where Azure is saying a provider does not support the API version the ELM is using to delete resources. The API version the ELM specifies is selected by the Azure SDK and it uses the latest supported version for that resource type. The list of supported versions is coming for Azure itself. The version selected is cached and it is not refreshed until a service (or the entire ELM) is restarted. This should be ok as these lists are pretty static and it would be unusual for a version to be removed.
I would restart the ELM to see if that fixes the problem, as that will cause the ELM to refresh what API versions it uses.
k
Keith Perri
05/27/2026, 4:27 PMOk, I'll give a reboot a try once I finish working on the few layers I currently have open. I'll update here once I'm to do so.
👍 1
Keith Perri
05/28/2026, 1:49 PMUnfortunately rebooting the ELM did not resolve this issue for us. I'm still randomly getting the above error message and having to manually clean up (delete) the packaging VMs after the capture is successful.
Keith Perri
05/28/2026, 10:06 PMUpdate, it seems to be working now, but I'll keep an eye on it. Maybe it was an issue on the Azure side.
t
Tyler Benoit
05/28/2026, 10:39 PMYeah, I was wrong about the caching. The values are cached per client and new client is created for each delete. I looked through the SDK and I can't see anything that would cause this nor any bugs fixed around this area. I can't really explain it other than Azure is deciding to return an invalid API version sometimes. Perhaps something to do with your subscription, enabled preview features or something. Perhaps they are rolling out a new version. I'm not sure.
k
Keith Perri
05/29/2026, 12:51 AMSpoke too soon, it stopped working again
t
Tyler Benoit
05/29/2026, 3:05 PMYup, I hit the same thing last night. The API is now returning
2026-03-01virtualMachines2026-03-01k
Keith Perri
05/29/2026, 10:45 PMThe issue is very sporadic, it seems to be working again, but then again who knows. Just glad it's not strictly a Citrix issue.