GetRunbook_Failed :: Bootstrap timeout - cluster failure during startup

Khaja_Zaffer — Fri, 05 Sep 2025 06:45:06 GMT

After creating a new workspace, if you come across

Failed to get instance bootstrap steps from the Databricks Control Plane. Please check that instances have connectivity to the Databricks Control Plane.
Instance bootstrap inferred timeout reason: GetRunbook_Failed

In the Base64 encoded failure message:
Failed to get runbook (may retry). Status code: 888. Content: HTTPSConnectionPool(host='eastus-c2.azuredatabricks.net', port=443): Max retries exceeded with url: /api/2.0/instances/vmboot/get_runbook (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f2c64c58f10>, 'Connection to eastus-c2.azuredatabricks.net timed out. (connect timeout=XX)'))

Why this issue is occured:

Network configuration would be the root cause, specifically, You must have enabled network subset link for the reference: private subnet feature.

You must have turned on the “Enable private subnet (no default outbound access)” option for the Databricks public subnet, which blocked its default outbound internet access.

The resolution would be :

You can fixed the issue by unchecking the private subnet option, which restored outbound access. After making this change, you can able to start the cluster without any problems.

topic GetRunbook_Failed :: Bootstrap timeout - cluster failure during startup in Community Articles

GetRunbook_Failed :: Bootstrap timeout - cluster failure during startup