Skip to content
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

Synapses Creating Big Data Pool validation error: Parameter 'BigDataPoolResourceInfo.node_count' failed to meet validation requirement. #14708

Closed
jayendranarumugam opened this issue Aug 7, 2020 · 7 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Synapse

Comments

@jayendranarumugam
Copy link

az feedback auto-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

@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Aug 7, 2020
@triage-new-issues triage-new-issues bot removed the triage label Aug 7, 2020
@ghost ghost added the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Aug 7, 2020
@yonzhan yonzhan added Synapse Service Attention This issue is responsible by Azure service team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 7, 2020
@ghost
Copy link

ghost commented Aug 7, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aim-for-better, @idear1203.

@yonzhan
Copy link
Collaborator

yonzhan commented Aug 7, 2020

synapse

@idear1203
Copy link
Contributor

Thanks for the notification. This is a bug. We will fix it soon.

@idear1203 idear1203 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Aug 7, 2020
@idear1203
Copy link
Contributor

idear1203 commented Aug 7, 2020

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.

@fengzhou-msft
Copy link
Member

@idear1203 you may need to add type=int in _params.py for node_count to pass the validation in SDK model.

@jayendranarumugam
Copy link
Author

jayendranarumugam commented Aug 15, 2020

Thank you all for fixing the bug. I just created another one MicrosoftDocs/azure-docs#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

@idear1203
Copy link
Contributor

Hi @jayendranarumugam , for the issue described on this page, we have already fixed it in the PR: #14755 . The fix will be available in the next Azure CLI release.

For MicrosoftDocs/azure-docs#60927 , this is a docs issue indeed. I have notified our PM for a fix. Thanks a lot for your feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Synapse
Projects
None yet
Development

No branches or pull requests

4 participants