- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2023 01:48 PM
Some follow up context.
I installed the Databricks CLI and set the target Azure Databricks host and PAT on a whim , and then re-ran the terraform and it looks like the cluster is being provisioned ... but ultimately fails due to the init script
Error: cannot create cluster: 0328-212215-kql46zgp is not able to transition from TERMINATED to RUNNING: An admin configured global init script failed. instance_id: 8ba71c27fbe54f3aa60799595954c3ce, databricks_error_message: Global init script mdp_init_script failed: Script exit status is non-zero, Termination info: code: GLOBAL_INIT_SCRIPT_FAILURE, type: CLIENT_ERROR, parameters: map[databricks_error_message:Global init script mdp_init_script failed: Script exit status is non-zero instance_id:8ba71c27fbe54f3aa60799595954c3ce]. Please see https://docs.databricks.com/dev-tools/api/latest/clusters.html#clusterclusterstate for more details
I would not expect the CLI as a requirement and a manual step to set the host and PAT, because I already do that in the Terraform code. Is this expected nature? If not, then how do I resolve the credential issue?