-
Notifications
You must be signed in to change notification settings - Fork 40
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
Unable to set local_ssd_count to 0 on cluster configuration #1258
Comments
It appears to be an issue on terraform provider side, DABs correctly generates the state with local_ssd_count set to zero
cc @mgyucht |
Thanks @andrewnester for this idea to check on the tfstate files. I now tried several times between 0 and non-zero values. |
@ne250040 yes, that's correct. We have to fix it on TF provider side first and upgrade it in CLI |
For visibility, here's required TF provider PR: databricks/terraform-provider-databricks#3385 |
## Changes Upgrade TF provider to 1.42.0 Also fixes #1258
Describe the issue
With the UI, I updated the cluster configuration to set the Number of Local SSDs as zero, the cluster seems runs normal. However, setting this value to 0 via Assets Bundle will revert the value to Default.
Configuration
With the below configuration, I see the cluster information on the job, where the Local SSD is set to 1 instead of 0
Steps to reproduce the behavior
Expected Behavior
When i setup local_ssd_count as 0 on the configuration, we expect the same.
Actual Behavior
Local SSD on the cluster configuration is 1 instead of 0.
OS and CLI version
CLI: Databricks CLI v0.214.0
OS: MacOS
Is this a regression?
This is a new setup, i'm not aware of previous versions.
Debug Logs
output_logs_sample.log
The text was updated successfully, but these errors were encountered: