-
Notifications
You must be signed in to change notification settings - Fork 384
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
[ISSUE] Cannot move cluster to auto-az #1700
Comments
We are experiencing this issue as well across 80+ AWS clusters. Manually have to edit the attribute in Databricks |
Thank you for the feature request! Currently, the team operates in a limited capacity, carefully prioritizing, and we cannot provide a timeline to implement this feature. Please make a Pull Request if you'd like to see this feature sooner, and we'll guide you through the journey. |
I have tried using auto in my databricks job (which also create clusters) and it works. The doc doesn't mention it, but it worked. I was using 1.6.5 when I tried it. |
I am currently facing this issue when deploying the Databricks Asset Bundle using GitHub CI/CD. Using I need to manually update the zone_id to update it to auto. |
Confirming this is still an issue on the latest provider version:
If the cluster exists and is set to a non-auto availability zone, but your template specifies |
Use of The CLI uses the below versions
|
Configuration
Expected Behavior
Changing "zone_id" from a specific value (ex: "us_east_1a") to "auto" actually changes the zone configuration for this cluster.
Actual Behavior
Changing "zone_id" from a specific value (ex: "us_east_1a") to "auto" does nothing. The zone stays on the previous specific value. In our case, this blocks us because we cannot start the cluster in this zone as we get AWS insufficient capacity errors. So we really want to move to "auto", even if that means recreating the cluster.
Seems like this behaviour was introduced with #937 to
prevent Terraform to restart a cluster which AwsAttributes.zone_id = "auto", as this is an unneeded/unwanted behavior.
, but we would argue that we really want the zone change to be applied.Steps to Reproduce
aws_attributes { zone_id = "us_east_1a" }
)aws_attributes { zone_id = "auto" }
)Terraform and provider versions
databricks/databricks 1.6.1
The text was updated successfully, but these errors were encountered: