Skip to content

direct: use AI Gateway services that a failed create request created - #7782

Merged
denik merged 3 commits into
mainfrom
direct-ai-gateway-create-recovery
Nov 18, 2026
Merged

denik merged 3 commits into
mainfrom
direct-ai-gateway-create-recovery

Conversation

@denik

@denik denik commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Create requests for mcp_services, model_provider_services and model_services (all AI Gateway) fail now and then with errors that leave it unknown whether the service was created. The direct engine now looks the service up after such an error, the same way recoverCreate does for features, serving endpoints and dashboards (#7757):

  • The service exists and was created by our request (create_time no earlier than a minute before the first request): use it.
  • It is missing: pause and repeat the create, up to retry.MaxRetries times. A repeat answered with 409 ALREADY_EXISTS means an earlier request landed, and the next lookup finds it.

recoverCreate now also treats these errors as uncertain, besides the 5xx/408 that retry.IsTransient covers. This applies to every resource that uses it:

  • 499 CANCELLED. The status is matched, not apierr.ErrCancelled, because a mapped error_code takes precedence over the status.
  • HTTP/2 stream resets (stream error: stream ID N; ...) that are not API errors.

The lookup after a failed create retries these errors as well.

Other changes:

  • libs/testserver now rejects a second MCP service, model service or model provider service with the same name with 409 ALREADY_EXISTS, as the cloud does (checked on AWS for model provider services), and sets create_time.
  • The retry warning no longer prints a double space for status codes that have no status text (retrying after 499 from ...).

Why

These errors hit the */lifecycle tests on main. Each one is a transient backend failure: the errors only come in 1–2 runs, and the AI Gateway backend has no visible pattern. Without recovery, a create that landed despite the error leaves a service that the next deploy fails to create. I chose a CLI recovery over a backend ticket because these errors are rare and transient. The PRs listed below took the same approach.

Judgment calls:

  • model_services has not hit these errors yet, but it uses the same create API; added on review. MCP and model services use the same AI Gateway backend. I assumed they answer a duplicate create with 409 ALREADY_EXISTS like model provider services; the probe ran only for model provider services.
  • The Lakebase recoveries (#7602, #7747, #7767) and vector search endpoints still use retry.IsTransient. Moving the "uncertain create" check into libs/retry for all of them can follow separately.

Dashboard

error snippet
error/479 cannot create resources.mcp_services.[NAME]: Storage timeout (504 DEADLINE_EXCEEDED)
error/484 cannot create resources.model_provider_services.[NAME]: (499 CANCELLED)
error/3770, error/3771, error/3777 model_provider_services: response body: stream error: stream ID N; INTERNAL_ERROR
error/3775 mcp_services: response body: stream error: stream ID N; INTERNAL_ERROR

Tests

  • New acceptance tests bundle/resources/{mcp_services,model_provider_services,model_services}/create_failure, covering:
    • a 504 after the service was created;
    • a 499 before it was created;
    • a 504 after creation followed by a lookup 404, so the repeated create gets 409 ALREADY_EXISTS;
    • for model provider services, a 499 on both the create and the first lookup.
  • A unit test for isUncertainCreateError.
  • Shared sdkTime helper for the create-time closures (also used by features).
  • The three */lifecycle tests pass on AWS with this change. They are named in the commit message for the PR's cloud run.

This pull request and its description were written by Isaac.

…est created

Create requests for mcp_services and model_provider_services fail
transiently (504 DEADLINE_EXCEEDED, 499 CANCELLED, HTTP/2 stream reset).
Look the service up and use it if the failed request created it, or
repeat the create while it is missing, as recoverCreate does for
features, serving endpoints and dashboards. recoverCreate now also
treats 499 and stream resets as uncertain.

aws: TestAccept/bundle/resources/mcp_services/lifecycle TestAccept/bundle/resources/model_provider_services/lifecycle

Co-authored-by: Isaac <no-reply@databricks.com>
@denik denik added the ai-auto Deprecated: use factory-generated instead. label Nov 18, 2026
aws: TestAccept/bundle/resources/mcp_services/lifecycle TestAccept/bundle/resources/model_provider_services/lifecycle

Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions github-actions Bot added the DABs DABs related issues label Nov 18, 2026
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Commit: 7a9207623 | Workflow run

Regression test report

Selected 3 changed tests (limit=20, 0 not selected)

12 tests: regression=6 unreleased=0 coverage=6 failing=0
test branch main (6109237) latest (v1.26.0)
TestAccept/bundle/resources/mcp_services/create_failure/DMS= ✅ ❌ ❌
TestAccept/bundle/resources/mcp_services/create_failure/DMS=true ✅ ❌ ❌
TestAccept/bundle/resources/mcp_services/lifecycle/DMS= ✅ ✅ ✅
TestAccept/bundle/resources/mcp_services/lifecycle/DMS=true ✅ ✅ ✅
TestAccept/bundle/resources/model_provider_services/create_failure/DMS= ✅ ❌ ❌
TestAccept/bundle/resources/model_provider_services/create_failure/DMS=true ✅ ❌ ❌
TestAccept/bundle/resources/model_provider_services/lifecycle/DMS= ✅ ✅ ✅
TestAccept/bundle/resources/model_provider_services/lifecycle/DMS=true ✅ ✅ ✅
TestAccept/bundle/resources/model_services/create_failure/DMS= ✅ ❌ ❌
TestAccept/bundle/resources/model_services/create_failure/DMS=true ✅ ❌ ❌
TestAccept/bundle/resources/model_services/lifecycle/DMS= ✅ ✅ ✅
TestAccept/bundle/resources/model_services/lifecycle/DMS=true ✅ ✅ ✅
TestAccept/bundle/resources/mcp_services/create_failure/DMS=: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/mcp_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmcp_servicescreate_failureDMS=1412094161/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.mcp_services.mcp1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/mcp-services?mcp_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 499 from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/936c57350bfc33a7.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/mcp_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmcp_servicescreate_failureDMS=2314939269/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.mcp_services.mcp1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/mcp-services?mcp_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 499 from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/ef98b48ae2e69675.json
TestAccept/bundle/resources/mcp_services/create_failure/DMS=true: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/mcp_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmcp_servicescreate_failureDMS=true288208127/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.mcp_services.mcp1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/mcp-services?mcp_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 499 from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/a036733e947a09f1.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/mcp_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmcp_servicescreate_failureDMS=true1218984953/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.mcp_services.mcp1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/mcp-services?mcp_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 499 from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.mcp_services.mcp1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/mcp-services
        -Created mcp_services.mcp1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //mcp-services
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/mcp-services
        -GET /api/2.1/unity-catalog/mcp-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/1435656766a08592.json
TestAccept/bundle/resources/model_provider_services/create_failure/DMS=: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_provider_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_provider_servicescreate_failu2606816105/002/output.txt
        @@ -3,53 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_provider_services.mps1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-provider-services?model_provider_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -
        -=== The create request is cancelled after creating the service and the first lookup is cancelled too: deploy repeats the lookup and uses the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/6907ac5912dfe66d.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_provider_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_provider_servicescreate_failu1553555786/002/output.txt
        @@ -3,53 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_provider_services.mps1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-provider-services?model_provider_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -
        -=== The create request is cancelled after creating the service and the first lookup is cancelled too: deploy repeats the lookup and uses the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/41381edec9e33d14.json
TestAccept/bundle/resources/model_provider_services/create_failure/DMS=true: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_provider_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_provider_servicescreate_failu3127303574/002/output.txt
        @@ -3,53 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_provider_services.mps1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-provider-services?model_provider_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -
        -=== The create request is cancelled after creating the service and the first lookup is cancelled too: deploy repeats the lookup and uses the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/a98b0e10ae6fd7ed.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_provider_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_provider_servicescreate_failu2407060446/002/output.txt
        @@ -3,53 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_provider_services.mps1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-provider-services?model_provider_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -
        -=== The create request is cancelled after creating the service and the first lookup is cancelled too: deploy repeats the lookup and uses the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 499 from GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_provider_services.mps1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-provider-services
        -Created model_provider_services.mps1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-provider-services
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-provider-services
        -GET /api/2.1/unity-catalog/model-provider-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/aa778af80e4b96ec.json
TestAccept/bundle/resources/model_services/create_failure/DMS=: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_servicescreate_failureDMS=3063909690/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_services.ms1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-services?model_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 499 from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/7706628908959958.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_servicescreate_failureDMS=436731032/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_services.ms1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-services?model_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 499 from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/sync-snapshots/3b32091e10492e76.json
TestAccept/bundle/resources/model_services/create_failure/DMS=true: branch ✅ | main (6109237) ❌ | latest (v1.26.0) ❌

main (6109237):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_servicescreate_failureDMS=tr2174377845/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_services.ms1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-services?model_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 499 from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/4e3a397da6ef4e3c.json

latest (v1.26.0):

acceptance_test.go:1388: Diff:
        --- bundle/resources/model_services/create_failure/output.txt
        +++ /tmp/TestAcceptbundleresourcesmodel_servicescreate_failureDMS=tr2569479048/002/output.txt
        @@ -3,39 +3,13 @@
         
         >>> [CLI] bundle deploy
         Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        +Error: cannot create resources.model_services.ms1: Fault injected by test. (504 DEADLINE_EXCEEDED)
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Endpoint: POST [DATABRICKS_URL]/api/2.1/unity-catalog/model-services?model_service_id=myservice&parent=schemas%2Fmain.myschema
        +HTTP Status: 504 Gateway Timeout
        +API error_code: DEADLINE_EXCEEDED
        +API message: Fault injected by test.
         
        -=== The create request is cancelled and the service was not created: deploy repeats the create
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 499 from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
         Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
         
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -
        -=== The create request times out after creating the service and the lookup misses it: the repeated create gets ALREADY_EXISTS and the next lookup finds the service
        -
        ->>> [CLI] bundle deploy
        -Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
        -Warn: deploying resources.model_services.ms1: retrying after 504 Gateway Timeout from POST /api/2.1/unity-catalog/model-services
        -Created model_services.ms1
        -Files: 1 uploaded, 0 deleted
        -Resources: 1 created, 0 changed, 0 deleted, 0 unchanged
        -
        ->>> print_requests.py --get //model-services
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        -POST /api/2.1/unity-catalog/model-services
        -GET /api/2.1/unity-catalog/model-services/main.myschema.myservice
        +Exit code: 1
        
    acceptance_test.go:1178: Test produced unexpected files:
        .databricks/.gitignore
        .databricks/bundle/default/deployment.json
        .databricks/bundle/default/resources.json
        .databricks/bundle/default/sync-snapshots/5b04506f58a34272.json

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 7a92076

Run: 44379826893

Env 🤯​MISS 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 281 22 9:49
💚​ aws-windows-latest-4core-16gb 1 283 20 6:12
🤯​ azure linux-2core-8gb 3 1 271 22 9:22
🤯​ azure-windows-latest-4core-16gb 3 1 273 20 6:53
🤯​ gcp linux-2core-8gb 3 1 272 22 11:16
🤯​ gcp-windows-latest-4core-16gb 3 1 274 20 5:19
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
🤯​ TestAccept/bundle/resources/mcp_services/lifecycle ✅​p ✅​p 🤯​M 🤯​M 🤯​M 🤯​M
🤯​ TestAccept/bundle/resources/model_provider_services/lifecycle ✅​p ✅​p 🤯​M 🤯​M 🤯​M 🤯​M
🤯​ TestAccept/bundle/resources/model_services/lifecycle ✅​p ✅​p 🤯​M 🤯​M 🤯​M 🤯​M
Top 11 slowest tests (at least 2 minutes):
duration env testname
3:55 gcp linux-2core-8gb TestImportDirDoesNotOverwrite
3:33 azure-windows-latest-4core-16gb TestAccept
3:18 aws-windows-latest-4core-16gb TestAccept
3:12 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir
3:08 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:55 aws linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
2:44 gcp-windows-latest-4core-16gb TestAccept
2:32 aws linux-2core-8gb TestAccept/bundle/resources/mcp_services/lifecycle/DMS=
2:10 azure-windows-latest-4core-16gb TestImportDirWithOverwriteFlag
2:09 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsRead
2:06 gcp linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir

@denik
denik marked this pull request as ready for review November 18, 2026 18:35
@denik
denik requested review from a team as code owners November 18, 2026 18:35

@review-oss-bot review-oss-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me — no issues found.

@Sankalp-Mittal Sankalp-Mittal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[AI Generated] Review by review-factory (Claude Opus 5.5 + Claude Fable 5.2, cross-verified). Only points the reviewers agreed on are posted.

Comment thread libs/testserver/mcp_services.go Resolved
aws: TestAccept/bundle/resources/mcp_services/lifecycle TestAccept/bundle/resources/model_provider_services/lifecycle TestAccept/bundle/resources/model_services/lifecycle

Co-authored-by: Isaac <no-reply@databricks.com>
@denik denik changed the title direct: use MCP and model provider services that a failed create request created direct: use AI Gateway services that a failed create request created Nov 18, 2026

@Sankalp-Mittal Sankalp-Mittal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[AI Generated] Follow-up review by review-factory (Claude Opus 5.5 + Claude Fable 5.2, cross-verified). Only points the reviewers agreed on are posted.

No new issues found.

@denik
denik added this pull request to the merge queue Nov 18, 2026
Merged via the queue into main with commit b5e4495 Nov 18, 2026
28 checks passed
@denik
denik deleted the direct-ai-gateway-create-recovery branch November 18, 2026 22:10
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

❌ Integration test report

Commit: b5e4495

Run: 44409094772

Env ❌​FAIL 🟨​KNOWN 🔄​flaky 💚​RECOVERED ✅​pass 🙈​skip Time
❌​ aws linux-2core-8gb 2 1 1 14 1628 1389 170:54
❌​ aws-windows-latest-4core-16gb 3 1 14 1544 1417 185:08
❌​ azure linux-2core-8gb 17 1 14 1594 1397 157:10
❌​ azure-windows-latest-4core-16gb 3 6 13 1520 1425 177:04
❌​ gcp linux-2core-8gb 2 1 14 1616 1395 167:32
❌​ gcp-windows-latest-4core-16gb 2 1 1 14 1531 1423 178:31
32 interesting tests: 17 FAIL, 12 RECOVERED, 2 flaky, 1 KNOWN
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
🟨​ TestAccept 🟨​K 🟨​K 🟨​K 💚​R 🟨​K 🟨​K
❌​ TestAccept/bundle/deployment/bind/alert ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deployment/bind/alert/DMS= ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deployment/bind/alert/DMS=true ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deployment/bind/dashboard ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deployment/bind/dashboard/DMS=true/READPLAN= ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/generate/alert ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/generate/alert/DMS= ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/generate/alert/DMS=true ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/basic ✅​p ✅​p ❌​F ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/basic/DMS= ✅​p ✅​p ❌​F 🔄​f ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/basic/DMS=true ✅​p ✅​p ❌​F 🔄​f ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/with_file ✅​p ✅​p ❌​F 🔄​f ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/with_file/DMS= ✅​p ✅​p ❌​F ❌​F ✅​p ✅​p
❌​ TestAccept/bundle/resources/alerts/with_file/DMS=true ✅​p ✅​p ❌​F 🔄​f ✅​p ✅​p
❌​ TestAccept/bundle/resources/apps/inline_config ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/apps/inline_config/DMS= ❌​F ❌​F ❌​F ❌​F ✅​p 🔄​f
❌​ TestAccept/bundle/resources/apps/inline_config/DMS=true 🔄​f ❌​F ❌​F ✅​p ❌​F ❌​F
💚​ TestAccept/bundle/resources/apps/lifecycle-started 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/basic 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/basic/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
🔄​ TestAccept/bundle/resources/postgres_synced_tables/recreate 💚​R 💚​R 💚​R 🔄​f 💚​R 💚​R
🔄​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS= 💚​R 💚​R 💚​R 🔄​f 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
Top 50 slowest tests (at least 2 minutes):
duration env testname
11:13 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
10:51 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
10:30 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:30 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:18 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
10:04 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:01 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:59 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:38 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:33 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:22 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:04 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:41 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:26 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:26 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
8:19 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
8:16 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
7:46 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:36 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:30 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:19 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
7:11 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:11 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
6:55 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:51 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:44 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:25 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=
6:19 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:14 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
6:09 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=true
6:06 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
5:55 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:51 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:48 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:45 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:30 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
5:30 azure-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
5:22 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:22 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:14 gcp-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
5:12 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:10 aws-windows-latest-4core-16gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
5:06 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:03 gcp linux-2core-8gb TestAccept/pipelines/run/refresh-flags
5:00 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:59 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:57 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true
4:55 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true
4:52 aws-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
4:51 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true

deco-sdk-tagging Bot added a commit that referenced this pull request Nov 19, 2026
## Release v1.27.0

### Notable Changes

 * `databricks aitools install`, `update` and `uninstall` now exit with code 1 when they do nothing they were asked to. `install` fails when it sets up nothing: no coding agent is detected, every agent is skipped or fails to install, or no skill in the release can be installed (also with `--path`). `update` fails when every update or check it attempts fails, and `uninstall` when every removal it attempts fails. Scripts that ran these commands as a best-effort step and relied on exit code 0 should handle the new exit code. ([#7481](#7481))
 * Add `file:<path>` selectors to `pipelines run` and pipeline `bundle run`. `--refresh` and `--full-refresh` now use space-separated lists, such as `--refresh "orders payments"`, instead of comma-separated lists. Single names containing spaces now require backticks, e.g. ``--refresh 'table:`order details`'``. ([#7184](#7184))
 * The Databricks CLI is now available on PyPI as `databricks`: run it with `uvx databricks`, or install it with `uv tool install databricks`, `pipx install databricks` or `pip install databricks`. The package contains only the prebuilt CLI binary. Uninstall the legacy `databricks-cli` package first, since both install a `databricks` command. ([#7704](#7704), [#7777](#7777))

### CLI

 * Add `databricks sandbox fs` commands (`cp`, `ls`, `cat`, `mkdir`, `rm`) to transfer files between your local filesystem and sandboxes using `<sandbox-id>:/path`. ([#7372](#7372))
 * `databricks fs` commands retry reads (stat, list, open) and deletes on DBFS and Volumes when the server returns a transient error or does not respond within the HTTP timeout. ([#7556](#7556))
 * Retry UC Volumes file operations (`fs cp`, `fs ls`, `fs rm`, bundle uploads to Volumes) when the Files API returns HTTP 408, 429, 502, 503 or 504 (for example "AWS S3 is throttling requests"), or on a transient network error; this regressed in v1.10.0. ([#7559](#7559))
 * Stop warning when the host metadata request (`/.well-known/databricks-config`) times out; the CLI already falls back to your config, and the message is still shown with `--debug`. ([#7752](#7752))
 * Add `databricks aitools auto-install disable` and `enable` to turn off (or back on) the automatic installation of Databricks AI tools on CLI upgrades. A global-scope `databricks aitools uninstall` also turns it off. ([#7701](#7701))
 * Stop printing the Databricks AI tooling install hint on `auth`, `configure`, `current-user me`, `version`, `help`, and shell-completion commands. ([#7452](#7452))
 * When Codex, Cursor, GitHub Copilot CLI, OpenCode, Gemini CLI, Antigravity, Pi, Goose or Kiro run the CLI without Databricks skills installed for that agent, the CLI now prints a one-line hint to install them with `databricks aitools install --agents <agent> --scope global`, previously shown only to Claude Code. ([#7586](#7586))
 * `databricks aitools install` now rejects an unknown `--agents` name before it shows the scope prompt, instead of after. ([#7469](#7469))
 * `databricks aitools install` no longer asks "Proceed?" after the agent picker; the picker selection confirms the plan. The picker title now shows the install scope, its hint says Enter installs, `--skills-only` runs label plugin agents "skills" and pre-check every agent whose config dir exists, and the plan summary after it is reduced to the scope line. ([#7478](#7478))
 * `databricks aitools install --output json` reports more specific `error_category` values: `SKILLS_FETCH_FAILED`, `RELEASE_LOOKUP_FAILED`, `RATE_LIMITED`, `MANIFEST_INVALID`, `STATE_INVALID` and `PLUGIN_CLI_TIMEOUT`. A coding agent CLI that does not answer in time is now reported as `timed out after <duration>`, followed by any stderr it wrote before it was stopped. ([#7475](#7475))
 * `databricks aitools install` no longer prompts when a coding agent runs it, even in a pseudo-terminal; it uses the non-interactive defaults instead and prints a note saying so. ([#7477](#7477))
 * `databricks aitools install` now prints the directory it installed skills into (for example `Installed 1 skill in ~/.databricks/aitools/skills.`), so agents can open the installed `SKILL.md` files without searching for them. ([#7668](#7668))
 * `databricks aitools install` now ends a failed install with a step to recover, in the text output and in a new `recovery` field of `--output json`. ([#7480](#7480))
 * `databricks aitools install` now installs plugins for the other coding agents even when installing skill files fails. ([#7479](#7479))
 * `databricks aitools install` now installs skill files for a detected coding agent whose CLI is not on PATH (for example a Claude Code desktop or IDE install), unless it already has the plugin, says how to switch to the plugin later, and warns when the current project also has the plugin. `databricks aitools update` no longer tries to install the plugin for such an agent, and no longer writes skill files next to a plugin that such an agent already has. ([#7482](#7482))
 * Fix `databricks aitools install` waiting a long time on an unreachable or slow workspace while it resolves authentication for telemetry; that wait is now limited to a few seconds. ([#7468](#7468))
 * `databricks aitools install`, `update` and `list` now refuse a skills manifest that names a skill or file outside the skills directory, before writing any skill files. A skill whose name or file paths are not portable is skipped with a warning, and `update` keeps its installed copy. ([#7722](#7722))
 * `databricks aitools install` and `databricks aitools update` refresh only the marketplace the Databricks plugin is listed in, so another unreachable marketplace no longer blocks them. When that refresh fails, both commands warn, install or update the plugin from the local copy of the marketplace, and record the plugin version as unknown. ([#7473](#7473))
 * `databricks aitools install` and `databricks aitools update` now wait up to 20 seconds instead of 5 for a coding agent's CLI to answer the plugin capability check, so a slow first start is less likely to report the agent as unavailable. ([#7472](#7472))
 * `databricks aitools install` no longer fails a plugin-only install when the lookup of the latest skills release on GitHub fails or is rate-limited. The plugin is installed and its version is recorded as unknown. ([#7474](#7474))
 * `databricks aitools` commands now send usage telemetry, and the CLI records when it recommends installing Databricks AI tools. When the configured workspace is slow or unreachable, `aitools install`, `update` and `uninstall` can take up to about 6 seconds longer, and `list`, `version` and runs that stop early up to about 3 seconds. Set `DATABRICKS_CLI_DISABLE_TELEMETRY=1` to opt out. ([#7467](#7467), [#7469](#7469), [#7470](#7470))
 * `databricks aitools install` and `databricks aitools update` now report a coding agent CLI shim (`.cmd` or `.bat`) on Windows that prints its plugin help and then exits with an error as `shim-exited-with-error`, with the command to run to see the error, instead of reporting the CLI as not on PATH. ([#7476](#7476))
 * `apps init` no longer suggests installing skills when every detected coding agent already has the Databricks plugin. ([#7467](#7467))
 * `databricks auth login` now gives up on the optional workspace lookup after about 5 seconds instead of retrying for about 5 minutes, and explains the fallback to the manual workspace ID prompt. ([#7522](#7522))
 * Throttle Claude Code's native plugin install hint separately from the text hint: it prints at most once per 10 minutes per session, so the install dialog still comes up when a subagent, a hook, or a command outside a Claude Code subprocess runs the session's first `databricks` command. ([#7692](#7692))
 * Print Claude Code's native plugin install hint alongside the text hint, so Claude Code offers a one-click install of the Databricks plugin. Claude Code now counts as having the tooling only when it loads it: skills only in `~/.databricks/aitools/skills` don't count, and a project- or local-scope plugin counts only when the CLI runs inside that project. `auth token`, `auth docker token` and CLI subprocesses no longer print install hints. ([#7585](#7585))
 * Interactive prompts and pagers now work in Git for Windows' bash and other MSYS2 shells when they run under ConPTY (the default since Git for Windows 2.47) or directly in a Windows console. ([#7699](#7699))
 * Add the `databricks feedback` command to send feedback about the CLI to Databricks. ([#7724](#7724))
 * Fix shell completion in `databricks fs` commands for local paths typed with a leading `./` or repeated separators, which previously offered no suggestions. ([#7679](#7679))
 * Fix a panic in `databricks labs` commands when a non-string SDK setting such as `DATABRICKS_DEBUG_HEADERS` or `DATABRICKS_RATE_LIMIT` is set in the environment. ([#7673](#7673))
 * Fix a panic in `databricks labs install` for projects whose `labs.yml` has no `install` section. ([#7673](#7673))
 * `NO_COLOR` no longer disables prompts, spinners or the list pager; they run without color. ([#7700](#7700))
 * Add the Beta `databricks pipelines test` command, which runs the tests of a pipeline, and the `testing` property of pipelines in bundles. ([#7429](#7429))
 * Add `databricks sandbox forward`, which serves an app running in a sandbox at a local URL. ([#7395](#7395))
 * Bound the whole telemetry upload at exit, including config resolution and authentication, by its timeout, so a stalled auth or telemetry endpoint no longer keeps a command from exiting. ([#7467](#7467))
 * `databricks version --check` now suggests `databricks aitools install` on stderr when a coding agent is detected without the Databricks plugin or skills. ([#7471](#7471))

### AI Runtime

 * `air get -o json` now reports `PENDING` while the run waits for compute, matching `air list`, and includes the run's `status_message`. ([#7455](#7455))
 * Wrap long failure reasons and log lines in the `air list` info and logs panes, keep the MLflow link (labeled with its retry) when a run's last retry failed before starting, and point `air logs` at earlier retries when the last one has no logs. ([#7456](#7456))
 * `databricks air logs --node` now reports an out-of-range node index when it can determine the run's node count, instead of looking like a successful run with no logs. ([#7516](#7516))
 * Add experiment, duration, accelerator, and dashboard metadata to `air list --output json`. For retried runs, `started_at` now reports the latest attempt, matching `air get`. ([#7568](#7568))
 * `air list` shortens MLflow run names and unnamed-run IDs by keeping their end behind a leading `…`, and its columns no longer overflow on wide (for example CJK) text; `air get` shows an unnamed run's full MLflow run ID. ([#7582](#7582))
 * Shrink the Experiment and User columns of the interactive `air list` table to fit the terminal width, keeping the end of a shortened experiment name. ([#7583](#7583))
 * Show the experiment, accelerators and configuration in the `air list` info pane for runs where it showed `N/A`. ([#7587](#7587))
 * Strip terminal control characters from the MLflow run, experiment and user names shown by `air list` and `air get`, so a run name cannot clear or retitle the terminal of whoever lists it. ([#7601](#7601))
 * `air logs`, `air get`, and `air run --watch` no longer make an extra credential-check request before fetching the run, and `air get` reuses the configured workspace ID instead of looking it up. ([#7613](#7613))
 * `air list` no longer waits on extra current-user requests before listing runs, which makes the default list about 150ms faster. ([#7615](#7615))
 * `air list --all-status` requests larger index pages, so it makes far fewer round trips once the server supports `page_size`. ([#7616](#7616))
 * Fit the interactive `air list` table to narrow terminals: when the Experiment and User columns are at their floors, shorten Started to `MM-DD HH:MM` and size the MLflow column to its labels, then hide Accelerators, User, MLflow and Progress in that order, naming the hidden columns in the hint line. ([#7629](#7629))
 * `air get -o json` now includes `mlflow_run_id` and `mlflow_experiment_id`, so a run can be handed to MLflow-based steps without parsing `mlflow_url`. They identify the MLflow run `mlflow_url` links to, including one from an earlier retry that `mlflow_retry` names. ([#7636](#7636))
 * `air get` and the `air list` info pane now show the environment of runs on the Databricks AI environment (`databricks_ai_v*`) instead of `N/A`. ([#7637](#7637))
 * `air run` now rejects a `code_source.include_paths` path that selects no files instead of uploading a snapshot without it; glob patterns and pathspec magic are left to git. ([#7643](#7643))
 * `air convert-to-dabs` now suggests the `--output-dir` that converts a working-tree workload whose `code_source.root_path` is outside the bundle directory, instead of suggesting `sync.paths`. ([#7644](#7644))
 * `air run` now lists a `code_source.root_path` outside a git repository relative to `root_path`, so running from a subdirectory of `root_path` no longer uploads an empty or partial snapshot. ([#7646](#7646))
 * `air list --all-status` now fills `--limit` past purged or inaccessible indexed runs. ([#7743](#7743))
 * `air run` now warns about missing PyTorch when a pinned snapshot's `include_paths` selects a Python file. ([#7744](#7744))
 * `air cancel JOB_RUN_ID` now rejects run IDs that are not AI Runtime runs instead of cancelling unrelated Jobs runs. In `-o json` output, the `failed[].error` text for a run that does not exist or that you cannot view now starts with `failed to get run <id>:` instead of the cancel API error. ([#7569](#7569))
 * `air get -o json` now reports `mlflow_retry` when the MLflow link comes from an earlier retry because the run's last retry never reached MLflow. ([#7620](#7620))
 * `databricks air run --help` now shows how to install the databricks-ai-runtime coding agent skill. ([#7652](#7652))
 * `air run --watch -o json` now reports each lifecycle `STATUS` transition once and never reports a non-terminal state after the run has ended, including when logs are served from MLflow artifacts. ([#7621](#7621))
 * `air convert-to-dabs` now explains the `--output-dir` workaround when `code_source.root_path` resolves to the bundle root, and notes when the generated job carries the default `max_retries`. ([#7579](#7579))
 * `air run` now refuses to upload a `code_source` snapshot that selects no files (for example when `root_path` is git-ignored) and explains the cause, and `--dry-run` runs the snapshot file selection and reports the file count. ([#7570](#7570))
 * Repeat the Jobs run link after live log streaming ends. ([#7571](#7571))
 * `air get -o json` includes run details including flat `accelerator_type` and `num_accelerators`. Use `--include-config` to include stored config, which may contain plaintext `env_variables` and parameters; downloads over 1 MiB are omitted, and config-dependent `max_retries` is otherwise null. ([#7624](#7624))
 * `air get` and the `air list` info pane no longer show `Max Retries 0` when the Jobs API leaves the task's retry limit out. For a run submitted with `air run`, the limit now comes from the run's uploaded config, shown as `3 (CLI default)` when the config doesn't set `max_retries`; it shows `N/A` when the limit can't be known (job runs, multi-container runs, legacy runs with no explicit value, or an unreadable config). ([#7623](#7623))
 * Reorganize `databricks air` help: subcommands are grouped by task, `air run` has examples, and YAML fields are listed under headings, with pool fields marked optional and `command`, `compute.num_accelerators`, and `compute.accelerator_type` correctly marked required. ([#7512](#7512))
 * `air run -h config` now lists the environment variables AI Runtime sets on every node (such as `MLFLOW_RUN_ID` and `CODE_SOURCE_PATH`), and `air logs --help` notes that `--download-to` cannot be combined with `--tail` or `--minutes`. ([#7655](#7655))
 * Support full workspace accelerator types in `air list` filters while preserving family matching, and reject invalid filter values. ([#7515](#7515))
 * `databricks air list --all-status` now warns when the AI Runtime run index is unavailable and it falls back to scanning Jobs runs. That fallback scan is capped at 250 runs, and a stuck index request fails after 15 seconds instead of retrying for minutes. `--all-status --filter user=<your email>` now uses the run index instead of scanning the workspace's full run history. ([#7619](#7619))
 * Return structured JSON errors for invalid `air list --filter` values when `-o json` is used. ([#7612](#7612))
 * `air list --all-status` no longer fails when a listed run has been purged. ([#7523](#7523))
 * **Behavior change:** `databricks air logs` now prints the logs available now and exits, also for an active run, matching `kubectl logs`, `docker logs` and `databricks apps logs`. Pass `--follow` (`-f`) to stream new lines until the run completes; `--tail N --follow` prints the last N lines first. `databricks air run --watch` still submits and streams. ([#7658](#7658))
 * `databricks air logs -o json` and `databricks air run --watch -o json` now emit a `WAITING` event, for example `{"type":"WAITING","message":"Waiting for accelerator compute capacity..."}`, when the reported waiting status changes. ([#7695](#7695))
 * `databricks air logs` on a run that ended in the last two minutes now waits for the log index to settle before printing, instead of sometimes dropping lines that were indexed late. ([#7663](#7663))
 * `air logs` and `air run --watch` now print the waiting status (for example `Waiting for accelerator compute capacity...`) as a line on stderr when stderr is not a terminal, instead of printing nothing until the run produces logs. ([#7657](#7657))
 * Route AIR log links to the MLflow Logs page instead of the hidden artifact path. ([#7491](#7491))
 * Invalid `compute.accelerator_type` errors and `air run -h config.compute` no longer list the CLI's built-in accelerator types, which could differ from the workspace's. ([#7520](#7520))
 * `databricks air --help` now notes that GPU pools are not required to run workloads. ([#7581](#7581))
 * `air run` now prints the job run URL with the `?o=<workspace-id>` suffix, matching `air get` and `air list`; `dashboard_url` in `air run -o json` and the `--watch` events gains it too. When `air list` cannot resolve the workspace ID, its links now omit `?o=` instead of ending in `?o=0`. ([#7573](#7573))
 * `databricks air run` now reports an unknown workload YAML key by its field path, suggests the closest valid field, and points to `-h config` instead of naming an internal Go type. ([#7574](#7574))
 * `air run` (including `--dry-run`) now warns before submitting when the `code_source` imports `torch` but PyTorch is not declared: the environment is the Standard environment (version 5 or later) with no `torch` dependency, so the run may fail after it waits for a GPU. ([#7656](#7656))

### Bundles

 * Add `isolation_mode` to the `catalogs` resource, so a catalog can be deployed as `OPEN` or `ISOLATED`. ([#7463](#7463))
 * `bundle validate` no longer warns when resource permissions and top-level or target permissions name the same principal. ([#7291](#7291))
 * Retry bundle file uploads, reads and deletes when the server does not respond within the HTTP timeout ("request timed out after ... of inactivity"). ([#7521](#7521))
 * Show how to recover when `bundle deploy` fails because an app's service principal does not exist or was deleted. ([#7533](#7533))
 * Retry transient server errors when creating Lakebase (`postgres_*`) resources in the direct deployment engine. ([#7557](#7557))
 * Fix `bundle plan` reporting the `spark_conf` and `custom_tags` the backend derives from `is_single_node: true` as drift on clusters. ([#7577](#7577))
 * Stop planning a spurious update for Lakeflow Connect pipelines whose `ingestion_definition.data_staging_options` is filled in by the backend. ([#7603](#7603))
 * Retry the root path check in `bundle destroy` on transient errors, so a dropped connection no longer fails the destroy. ([#7597](#7597))
 * Use the Lakebase branch when its create request times out but the branch was created, instead of failing the deploy, in the direct deployment engine. ([#7602](#7602))
 * Retry transient server errors when deleting resources in the direct deployment engine. ([#7708](#7708))
 * Use the Lakebase project when its create request times out but the project was created, instead of failing the deploy with "already exists", in the direct deployment engine. ([#7747](#7747))
 * Use the feature, model serving endpoint or dashboard that a create request created despite timing out, instead of failing the deploy, in the direct deployment engine. ([#7757](#7757))
 * Use the Lakebase role when its create request fails with a transient error but the role was created, instead of failing the deploy, in the direct deployment engine. ([#7767](#7767))
 * Use the MCP service, model service or model provider service that a create request created despite failing with a timeout, a 499 or a reset stream, instead of failing the deploy, in the direct deployment engine. Create recovery for features, serving endpoints and dashboards now also covers 499 and reset streams. ([#7782](#7782))
 * Retry app updates and deletes in the direct deployment engine when they fail with 400 BAD_REQUEST because the app compute is `UPDATING`, after waiting for the compute to settle. ([#7606](#7606))
 * Enable drift detection for `source_code_path` and `git_source` on apps. ([#6399](#6399))
 * `bundle destroy` and `bundle deploy` no longer fail with "internal error, missing in state" when the state holds an empty-ID entry left by an interrupted recreate in an older CLI. ([#7676](#7676))
 * Fix a feature whose `full_name` contains uppercase letters being recreated on every deploy. ([#7398](#7398))
 * Fix `bundle deployment bind` (and `bundle generate --bind`) failing with `no such node "resources.internal_immutable_snapshots.immutable"` when `workspace.sync_mode` is `immutable`, as reported in [#7306](#7306). ([#7329](#7329))
 * Retry creating the deployment lock (without `--force-lock`) when the request fails with a transient server error, times out ("request timed out after ... of inactivity") or loses its connection ("unexpected EOF"). ([#7594](#7594))
 * Fix a materialization set member whose `feature_name` contains uppercase letters failing to deploy, or recreating the set on every deploy. ([#7398](#7398))
 * Delete the old resource when its name follows a renamed schema. ([#7718](#7718))
 * Fix `pipelines dry-run` starting a real run when given a job KEY, and a crash in its shell completion. ([#7672](#7672))
 * Rename schemas in place; schemas and volumes follow a renamed catalog or schema. ([#7343](#7343))
 * Fix a panic when validating or deploying jobs with local libraries and serverless job clusters. ([#7725](#7725))
 * Fix `tgz` artifacts with `git` set producing an empty tarball or failing when the bundle is in a subdirectory of the git repository. ([#7674](#7674))
 * Apply `presets.trigger_pause_status` and the development mode pause default to `triggers[]` entries on jobs. ([#7450](#7450))

### Dependency Updates

 * Bump dependencies with known vulnerabilities. ([#7750](#7750))
 * Update the Go SDK to [v0.198.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.198.0). ([#7530](#7530))
 * Update the Go SDK to [v0.199.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.199.0). ([#7584](#7584))
 * Update the Go SDK to [v0.200.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.200.0). ([#7653](#7653))
 * Update the Go SDK to [v0.201.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.201.0). ([#7769](#7769))
@denik denik added factory-generated and removed ai-auto Deprecated: use factory-generated instead. labels Nov 20, 2026
idelafuente-oc pushed a commit to idelafuente-oc/cli that referenced this pull request Nov 20, 2026
…abricks#7801)

## Changes

Lakebase catalog creates now recover from transient errors the way
postgres branches, projects and roles already do
([databricks#7602](databricks#7602),
[databricks#7747](databricks#7747),
[databricks#7767](databricks#7767)). Until now,
`database_catalogs` and `postgres_catalogs` failed the deploy on any
create error. If the catalog had actually been created, the next deploy
also failed, with "already exists".

- **postgres_catalogs**: on a transient error (5xx, 408, inactivity
timeout), `recoverPostgresCreate` looks the catalog up. It uses the
catalog if its `create_time` shows this deployment created it, and
repeats the create while the catalog is missing. This is the same code
path roles use.
- **database_catalogs**: these use the generic `recoverCreate`, as
features, serving endpoints and AI Gateway services do
([databricks#7757](databricks#7757),
[databricks#7782](databricks#7782)). The Database API
returns no create time, so the time check uses `created_at` of the Unity
Catalog catalog the database catalog registers. I checked on AWS that it
is there, with `catalog_type: MANAGED_ONLINE_CATALOG`. If the database
catalog exists but its UC catalog can't be found, the deploy fails with
"has no create time" rather than repeating the create.
- Both APIs answer a duplicate create with `400 CATALOG_ALREADY_EXISTS`
("Catalog '...' already exists"; checked on AWS).
`isPostgresAlreadyExists` already matches that response.
`isAlreadyExists` now matches it as well, so a repeated database catalog
create that lands after an earlier one triggers another lookup.

Testserver, to match the cloud:
- A database catalog create also registers the UC catalog with
`created_at`, and the delete removes it.
- A missing database catalog returns `404 CATALOG_DOES_NOT_EXIST`
instead of a plain-text 404. Without the error code the SDK doesn't
report it as missing.
- A duplicate database or postgres catalog returns `400
CATALOG_ALREADY_EXISTS`, not 409 or silently overwriting.

Judgment calls:
- postgres_catalogs gates recovery on `retry.IsTransient`, like its
postgres siblings, not on the wider `isUncertainCreateError` (499,
stream resets). Neither of those has been seen on Lakebase creates.
- A recovered postgres catalog is used as soon as GET finds it, as with
roles. The catalog has no readiness state to wait on.

## Why

These create errors fail cloud runs on main. The two dashboard errors
this PR fixes:

## Dashboard

| error | failure |
|---|---|
|
[error/2208](http://go/cli/dashboard/error/2208?main=1&pr=1&end=2026-11-19T10:00:00Z&last=30d)
| `Error: cannot create resources.database_catalogs.my_catalog: (504
DEADLINE_EXCEEDED)` (Azure, 4 failures since 2026-10-26) |
|
[error/3554](http://go/cli/dashboard/error/3554?main=1&pr=1&end=2026-11-19T10:00:00Z&last=14d)
| `Error: cannot create resources.postgres_catalogs.my_catalog: The
request could not be processed. Please try again later and contact
Databricks if the problem persists. [TraceId: [TRACE_ID]] (500
INTERNAL_ERROR)` (AWS, GCP) |

Tests:
[TestAccept/bundle/resources/synced_database_tables/basic/DMS=](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/synced_database_tables/basic/DMS=?main=1&pr=1&end=2026-11-19T10:00:00Z&last=30d),
[TestAccept/bundle/resources/synced_database_tables/basic/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/synced_database_tables/basic/DMS=true?main=1&pr=1&end=2026-11-19T10:00:00Z&last=30d),
[TestAccept/bundle/resources/postgres_synced_tables/basic/DMS=true](http://go/cli/dashboard/test/acceptance.TestAccept/bundle/resources/postgres_synced_tables/basic/DMS=true?main=1&pr=1&end=2026-11-19T10:00:00Z&last=14d)

## Tests

- New acceptance tests use injected faults:
`database_catalogs/create_504` covers a catalog created despite a 504, a
catalog that was not created, a catalog that only shows up after the
repeat hits "already exists", and an unreadable catalog.
`postgres_catalogs/create_transient_500` covers created, not created
(504) and unreadable.
- Unit tests cover catalogs that predate the deploy (not taken over), a
missing create time, and a missing UC catalog.
- Ran the full local acceptance suite. Probed on AWS with `testme-aws`:
UC `created_at` on a database catalog, and the duplicate-create error
from both APIs.

This pull request and its description were written by Isaac.

---------

Co-authored-by: Isaac <no-reply@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DABs DABs related issues factory-generated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants