Skip to content
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

Bundle deploy / destroy errors on a few jobs only #2256

Open
cptshrk108 opened this issue Jan 29, 2025 · 3 comments
Open

Bundle deploy / destroy errors on a few jobs only #2256

cptshrk108 opened this issue Jan 29, 2025 · 3 comments
Labels
DABs DABs related issues

Comments

@cptshrk108
Copy link

Describe the issue

When using the deploy or destroy command, certain jobs are not getting created or deleted. The jobs are never the same one, and it's only ever 5-10 on a total of 100.

Running the command a second time will create or destroy the remaining jobs.

Configuration

Using the commands from local to a testing environment where no other jobs or bundles can conflict. None of the jobs are running or modified.

Steps to reproduce the behavior

Please list the steps required to reproduce the issue, for example:

  1. Run databricks bundle deploy ...
    or
  2. Run databricks bundle destroy...
  3. See error

Expected Behavior

All jobs go through.

Actual Behavior

Some jobs don't go through

OS and CLI version

Databricks CLI v0.239.1

Is this a regression?

Same error on Databricks CLI v0.236.0

Debug Logs

Error: terraform apply: exit status 1

Error: cannot delete job: 


Error: cannot delete job: 


Error: cannot delete job: 


Error: cannot delete job: 


Bundle destroy successfully.
@cptshrk108 cptshrk108 added the DABs DABs related issues label Jan 29, 2025
@pietern
Copy link
Contributor

pietern commented Jan 29, 2025

Thanks for reporting the issue.

Does the output not include any error messages?

I suspect this could be related to some kind of rate limiting, but haven't seen this before.

@cptshrk108
Copy link
Author

No other errors no. I get the regular logging, where all affected jobs are listed, then the operation starts, then the only error is what I posted. The jobs are not named, but they are still present in the workspace. Running the command a second time deletes/creates them.

@cptshrk108
Copy link
Author

cptshrk108 commented Jan 29, 2025

The creation error is a bit more verbose, but not any more details :


Error: cannot create job: 

  with databricks_job.star-slv-lnd-slv-dom,
  on bundle.tf.json line 33893, in resource.databricks_job.star-slv-lnd-slv-dom:
33893:       },


Error: cannot create job: 

  with databricks_job.tpa-raw-ini-brz-init,
  on bundle.tf.json line 35802, in resource.databricks_job.tpa-raw-ini-brz-init:
35802:       },


Error: cannot create job: 

  with databricks_job.virage-brz-inc-brz-mrg,
  on bundle.tf.json line 38097, in resource.databricks_job.virage-brz-inc-brz-mrg:
38097:       },


Error: cannot create job: 

  with databricks_job.virage-raw-inc-brz-lnd,
  on bundle.tf.json line 43642, in resource.databricks_job.virage-raw-inc-brz-lnd:
43642:       },


Error: cannot create job: 

  with databricks_job.virage-raw-ini-brz-lnd,
  on bundle.tf.json line 45509, in resource.databricks_job.virage-raw-ini-brz-lnd:
45509:       },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DABs DABs related issues
Projects
None yet
Development

No branches or pull requests

2 participants