-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
az vmss deployment failing with "Parameter 'virtualMachineProfile' is not allowed" #27806
Comments
Thank you for opening this issue, we will look into it. |
Hi @TheOnlyWei, I cannot repro this issue. Could you please run it again? |
@yanzhudd Did you run it in Azure Stack Hub or Azure Cloud? |
@TheOnlyWei -- The error message doesn't appear to be related to any changes to the And the error message doesn't match the language used by Azure Resource Manager for unrecognized parameters. |
Hi @TheOnlyWei, Has this issue been solved? I successfully created the resource using this command with 2020-09-01-hybrid API profile
This error means you need to delete the previous resource or change vmssNmae and recreate it, could you please try again? |
@Jing-song Strange, I ran the following and got no VMSS:
I had to change the name to make it work. So, it still seems like there is an issue because
Also, do you know why |
Could you please provide the
The earliest swagger version(#16666) of |
@TheOnlyWei, |
@Jing-song @yanzhudd |
@Jing-song @yanzhudd Would also be helpful if the error was clearer on requiring
|
Hi @TheOnlyWei, thanks for raising this. To clarify on the issue here:
Thanks! |
@hilaryw29 Before the default value is changed, |
@Jing-song Pardon my ignorance, I want to make sure I have a correct understanding of the problem here:
If orchestration mode cannot be set to Flex for any customer on 2018-03-01-hybrid, 2020-09-01-hybrid API profiles (i.e. this is not an issue specific to Azure Stack Hub), then we should make sure that there is logic in place to keep |
@hilaryw29 |
Hi @Jing-song, before we make any changes, let me reach out to Azure Stack Hub contacts to look into this further. Will let you know once we decide on next steps here. Thanks! |
Hi @Jing-song, based on discussion with Azure Stack Hub in email thread, I believe your proposal above works. Would it be possible to update CLI behavior such that orchestration-mode can only be set to "uniform" for all API profiles before 2020-12-01? Thanks! |
@hilaryw29 |
Describe the bug
az vmss deployment failing with "Parameter 'virtualMachineProfile' is not allowed". We use the Azure CLI 2.54.0 nightly build:
https://aka.ms/InstallAzureCliWindowsEdge
The environment is Azure Stack Hub with 2020-09-01-hybrid API profile. Either VMSS or Resource Deployment is the root cause.
Hi @yanzhudd @Jing-song, was there any change from VM side that could have caused this in the nightly build?
Hi @anthony-c-martin @jeskew, were there any changes from Resource Deployment side that could have caused this in the nightly build?
Related command
Errors
Issue script & Debug output
Command
az vmss create -g $vmssRgName -n $vmssName --admin-username $vmssAdminUserName --admin-password $vmssAdminPassword --image $imageName --authentication-type password --upgrade-policy-mode $upgradeMode --debug
Debug
I had to truncate to the last part of the debug because I cannot fit the entire message length of characters in this issue post.
Expected behavior
Should have no errors.
Environment Summary
Additional context
I noticed a breaking change for
az vmss create
:https://techcommunity.microsoft.com/t5/azure-compute-blog/breaking-change-for-vmss-powershell-cli-customers/ba-p/3818295
The commit for Azure CLI was 2 days ago from this post: d72b6ce
So, I set the
--orchestration-mode
toUniform
:but I get a new error:
The text was updated successfully, but these errors were encountered: