TooManyExtensionProviders

[auwi987]

Related command
az vm create -g <Resource_Group_Name> -n <VM_Name> --attach-os-disk <Os_Disk_ID> --os-type "windows" -- --patch-mode "Manual"

Describe the bug

{
    "status": "Failed",
    "error": {
        "code": "TooManyExtensionProviders",
        "message": "The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers."
    }
}

To Reproduce
I'm trying to spin up a VM from an existing managed OsDisk via Az CLI. the original VM where OsDisk previously tied up has 12 VM extensions. now the error is giving me the impression that once you spin this, any extension from the previous VM via Az CLI script will automatically be included in the VM creation. but on portal, this is not a problem because it will automatically set to "none"

Expected behavior
create a vm image using existing OsDisk

azure cli link https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-create
also there is no flag to set vm extension to "none"

was there any solution to this??

[auwi987]

originally i posted it here https://github.com/MicrosoftDocs/azure-docs/issues/23934

[yonzhan]

@zhoxing-ms for awareness

Thank you for your feedback. This has been routed to the support team for assistance.

[zhoxing-ms]

I'm trying to spin up a VM from an existing managed OsDisk via Az CLI. the original VM where OsDisk previously tied up has 12 VM extensions. now the error is giving me the impression that once you spin this, any extension from the previous VM via Az CLI script will automatically be included in the VM creation.

Since CLI uses the ARM template deployment to create VM, so there is no such logic on client side
This should be a REST service issue, and the Compute team needs to investigate it

[auwi987]

I'm trying to spin up a VM from an existing managed OsDisk via Az CLI. the original VM where OsDisk previously tied up has 12 VM extensions. now the error is giving me the impression that once you spin this, any extension from the previous VM via Az CLI script will automatically be included in the VM creation.

Since CLI uses the ARM template deployment to create VM, so there is no such logic on client side This should be a REST service issue, and the Compute team needs to investigate it

do we need to create separate ticket for this or can someone from you guys reroute this to the right channel? all i know is im using azure cli and i dont know as well the exact translation from cli to rest service behind so i dont know how to explain it to the channel you're mentioning.

[zhoxing-ms]

do we need to create separate ticket for this or can someone from you guys reroute this to the right channel? all i know is im using azure cli and i dont know as well the exact translation from cli to rest service behind so i dont know how to explain it to the channel you're mentioning.

Sorry, I just explained this is a server related issue, and we will route it to the appropriate service team

@nkuchta Could you please take a look at the VM extension related issue? Or do you know who is the right person to investigate this issue?

[nkuchta]

This has nothing to do with VM extensions. From what I can tell it is related to the ARM request itself.

…

On Thu, Sep 8, 2022, 7:46 PM Xing Zhou ***@***.***> wrote: do we need to create separate ticket for this or can someone from you guys reroute this to the right channel? all i know is im using azure cli and i dont know as well the exact translation from cli to rest service behind so i dont know how to explain it to the channel you're mentioning. Sorry, I just explained this is a server related issue, and we will route it to the appropriate service team @nkuchta <https://github.com/nkuchta> Could you please take a look at the VM extension related issue? Or do you know who is the right person to investigate this issue? — Reply to this email directly, view it on GitHub <#23796 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEU3DVCOCIHQK7RNHB2TUDV5KQJFANCNFSM6AAAAAAQGJV7DE> . You are receiving this because you were mentioned.Message ID: ***@***.***>