You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: },
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:
databricks bundle deploy ...
or
databricks bundle destroy...
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
The text was updated successfully, but these errors were encountered: