az feedbackauto-generates most of the information requested below, as of CLI version 2.0.62
Describe the bug
Running the command of creating bigdata pools for azure synapses getting the below error
validation error: Parameter 'BigDataPoolResourceInfo.node_count' failed to meet validation requirement.
To Reproduce
Download latest az cli and running the below command which was the example given at here
az synapse spark pool create --name testpool --workspace-name testsynapseworkspace --resource-group rg \
--spark-version 2.4 --node-count 3 --node-size Medium
Expected behavior
It should create a Big data pool
Environment summary
Windows 10
Additional context
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aim-for-better, @idear1203.
synapse
Thanks for the notification. This is a bug. We will fix it soon.
I am able to repro the issue in Cloud Shell but not able to repro it on my local machine.
az synapse spark pool create --name testpool--workspace-name testsynapseworkspace --resource-group rg --spark-version 2.4 --node-count 4 --node-size Medium
Command group 'synapse' is in preview. It may be changed/removed in a future release.
validation error: Parameter 'BigDataPoolResourceInfo.node_count' failed to meet validation requirement.
It might related to code here: https://github.com/Azure/azure-cli-extensions/blob/master/src/synapse/azext_synapse/vendored_sdks/azure_mgmt_synapse/models/_models_py3.py#L317 . But I don't understand why the error is reported.
With --debug, I see the error is thrown from cli.azure.cli.core.util
cli.azure.cli.core.util : validation error: Parameter 'BigDataPoolResourceInfo.node_count' failed to meet validation requirement.
validation error: Parameter 'BigDataPoolResourceInfo.node_count' failed to meet validation requirement.
@idear1203 you may need to add type=int in _params.py for node_count to pass the validation in SDK model.
Thank you all for fixing the bug. I just created another one https://github.com/MicrosoftDocs/azure-docs/issues/60927. Not sure really it is a bug in the code or docs issue. Just putting it here FYI. Thanks again!
Cc: @idear1203 @fengzhou-msft
Hi @jayendranarumugam , for the issue described on this page, we have already fixed it in the PR: https://github.com/Azure/azure-cli/pull/14755 . The fix will be available in the next Azure CLI release.
For https://github.com/MicrosoftDocs/azure-docs/issues/60927 , this is a docs issue indeed. I have notified our PM for a fix. Thanks a lot for your feedback!