Unable to run jobs with git notebooks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 02:22 PM
So, in this case our jobs are deployed from our development workspace to our isolated testing workspace via an automated Azure DevOps pipeline. As such, they are created (and thus run as) a service account user.
Recently we made the switch to using git-based notebooks in our jobs from notebooks stored in the workspace itself. After granting the service account proper access to the repository, configuring it's git integration within the workspace, and turning repositories on for this workspace, we ran into the following error:
Failed to checkout Git repository: RESOURCE_DOES_NOT_EXIST: RESOURCE_DOES_NOT_EXIST: Parent directory /Repos/.internal does not exist.
Some other discussions in this community lead me to believe it is an internal databricks issue.
- Labels:
-
Azure
-
Azure databricks
-
JOBS
-
Notebooks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 02:25 PM
As a workaround, I was able to get jobs to run in this workspace by first running a cloned copy of a failing job as myself. This seems to have created the missing resources/directories that the failed jobs required. Subsequent re-runs of the failed jobs under the service account have been successful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2023 01:41 AM
Hi @Chris Block
Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help.
We'd love to hear from you.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2023 12:01 PM
@Vidula Khanna As I stated previously in my reply, I was able to work around the issue. I do not think that the workaround constitutes a solution, so I do not believe it should be marked as the proper resolution of the issue.

