topic Re: GIT integration with Lakehouse not working this morning in Data Engineering

GIT integration with Lakehouse not working this morning

Amit_K — Wed, 15 Jan 2025 15:16:32 GMT

Hi,

I have a workspace with Warehouse and Lakehouse in there and until this morning, the workspace was nicely integrated with git. That is sync to and update from git were just working fine.

But all of a sudden, the git inetgration is not working with the workspace now. Neither can sync from or sync to git. No clear error but just " Something went wrong " or "Unable to update workspace" .

I have tried mapping the branch to a new workspace and still the same issue.

If I drop the Lakehouse from Git branch ( only a meta file anyways) , commit and then try to sync , then workspace gets updated.

So, it seems some kind of release or on-going-work by the fabric dev team, has broken the git inetgration with workspaces having lakehouses.

Is someone else facing the same issue . It started for me this morning GMT at around 9 AM

Thanks.

Re: GIT integration with Lakehouse not working this morning

Amit_K — Wed, 15 Jan 2025 19:35:12 GMT

Is no one else facing the issue? I am unable to sync or update any workspace which has a lakehouse in it. I need the lakehouse and warehouse in the same workspace to be able to run cross database queris during data transformation. I am sure others may be using the same set-up.

Re: GIT integration with Lakehouse not working this morning

Sam_ — Wed, 15 Jan 2025 20:48:39 GMT

I am experiencing exactly the same issue, I am unable to commit a lake house resource to GitHub or azure devops. Hopefully this is fixed promptly.

Re: GIT integration with Lakehouse not working this morning

Amit_K — Thu, 16 Jan 2025 05:48:35 GMT

seems to be working now. Would massively appreciate, if microsoft stops breaking things which are key to CI/CD in fabric

Re: GIT integration with Lakehouse not working this morning

Anonymous — Fri, 17 Jan 2025 14:45:10 GMT

I'm having the same exact issue. When trying to sync a workpace that previously worked perfectly, I'm getting an error. I tried disconnecting from existing repository and try to sync into a new one and it worked. I was able to commit all items in the workspace exept a Lakehouse. I created a new lakehouse to test my theory and it did not let me sync it either.

Have you been able to solve this issue?

Re: GIT integration with Lakehouse not working this morning

Amit_K — Fri, 17 Jan 2025 15:15:17 GMT

It auto-resolved after a day. I am pretty sure some microsoft dev has released a changed which is breaking the lakehouse integration. It went away for me after a day but it was a day of real anxiety for me atleast. Check again after a few hours or may be tomm

Re: GIT integration with Lakehouse not working this morning

Anonymous — Fri, 17 Jan 2025 15:37:26 GMT

Thank you very much for your response. I'll continue to monitor it.

Re: GIT integration with Lakehouse not working this morning

CJG2090 — Sat, 18 Jan 2025 04:02:10 GMT

I am having the same issue and still am not able to sync the Lakehouse to DevOps. Only the Lakehouse is erroring.

Re: GIT integration with Lakehouse not working this morning

v-achippa — Mon, 20 Jan 2025 12:18:51 GMT

Hi @Amit_K,

Thank you for reaching out to Microsoft Fabric Community.

As we haven’t heard back from you, we wanted to kindly follow up to check if the issue is resolved. or let us know if you need any further assistance!
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Anjan Kumar Chippa

Re: GIT integration with Lakehouse not working this morning

Anonymous — Mon, 20 Jan 2025 15:06:55 GMT

Hello, I do have the same issue, also only with the Fabric Lakehouses.

When updating via Git Sync :

<plaintext> Error response: { "errorCode": "Git_InvalidResponseFromWorkload", "message": "An error occurred while processing the operation", "relatedResource": { "resourceId": "xxx", "resourceType": "Lakehouse" } } </plaintext>

I am using a mix of these PS scripts, for polling the long operation when syncing :

fabric-samples/features-samples/git-integration/GitIntegration-UpdateFromGit.ps1 at main · microsoft/fabric-samples · GitHub

fabric-samples/features-samples/fabric-apis/LongRunningOperation-Polling.ps1 at main · microsoft/fabric-samples · GitHub

And on the GUI, when clicking on Update all (only a Lakehouse in the change list) , I got the following pop up :

<plaintext>Title: Operation Blocked Content: We couldn't complete this request because the items in the following list have a reserved name. Try again later. </plaintext>

Re: GIT integration with Lakehouse not working this morning

afraaij_Amphia — Tue, 21 Jan 2025 08:03:01 GMT

I think everybody is facing this issue.

Fabric lakehouse schema objects ar not yet part of the Git integration.
We face the same issue:

- Personal development workspace

- Has a Lakehouse and Warehouse with views using Lakehouse tables

- Git integrated

- Commit to Git

- Go to the integration test workspace to get from the main branch the updates done during development

- Update fails because of delta tables missing in the lakehouse

- The Lakehouse in Git only contains naming of the lakehouse the lakehouse.metadata.json is empty

When will Microsoft fix this or what is there workarround?

Re: GIT integration with Lakehouse not working this morning

BenjaminSchenk — Tue, 21 Jan 2025 10:04:00 GMT

I can also reproduce this error in my workspaces. It occurred for the first time this morning. Yesterday afternoon, everything was still running correctly.

Re: GIT integration with Lakehouse not working this morning

Amit_K — Tue, 21 Jan 2025 18:03:38 GMT

Think , this issue is surfacing in different regions one by one. I have not faced this issue anymore since last Thursday. So it tells me that the fix or rollback (whatevr) is also getting released region by region. Strange that no one from microsoft has replied on this thread to assure everyone on the issue. It wasted one day or my time and it seems many people are trying to address it by lengthy workarounds which may become redundant once the issue is fixed.

Re: GIT integration with Lakehouse not working this morning

timahenning2 — Tue, 21 Jan 2025 21:17:48 GMT

Previously working Fabric workspaces with Lakehouses integrated to Azure DevOps Git repos are failing with the 'Something went wrong' error message. My tenant is in 'North Central US (Illinois)'. It started with one workspace and then eventually all workspaces in the tenant integrated to Git are failing to sync. Looking at the network calls in the browser dev tools, the Fabric UI git status response was a 400 after selecting the 'Sync branch' button.

I noticed the workspace/git/status API calls were failing and returned a 400 code. I tried to call git/status myself using the Fabric API and the error message said I needed to initialize the workspace. So I tried.

https://api.fabric.microsoft.com/v1/workspaces/<my workspace id>/git/initializeConnection

body payload

{
"initializationStrategy": "PreferRemote"
}

Here is the 400 response

{
  "requestId": "06c9683e-e02c-433d-8797-d6f6a9704708",
  "errorCode": "InvalidDefinitionFormat",
  "message": "Requested item definition format is invalid"
}

Maybe I do not have the correct body payload parameters. If I do, then Microsoft should fix this API call.

Re: GIT integration with Lakehouse not working this morning

Amit_K — Tue, 21 Jan 2025 19:06:35 GMT

The reserved nAe error is normally a transient one. May be you deleted a LH with same nme and syncing back a LH with the same name from Git

Re: GIT integration with Lakehouse not working this morning

linsonabr — Wed, 22 Jan 2025 01:51:24 GMT

We have the same issue. Git sync is not working. Tried disconnecting and reconnecting git, restarting capacity. Even deleted and created workspace.
Error is "Unable to initialize workspace". Our capacity is in East US 2.

Re: GIT integration with Lakehouse not working this morning

OZaharia — Wed, 22 Jan 2025 06:42:44 GMT

Same here, is there a working workarround for this, or we just need to wait and hopefully the functionality will be restored at some point with no time frame at the horizon?

For me it started to fail like this aprox 24 hours ago (at the moment I am writing this message). Also, in the developer console of the browser I have intercepted a message Invalid artifact definition format: LakehouseGit. In all the metadata and .platform files stored in GIT I don't have this type written.

Also, what I observed is that, now, the Lakehosue and Warehouse created when a dataflow gen 2 is created, are no longer visible in the Source Control tab when there is a dataflow present in the workspace. Could these be related?

Re: GIT integration with Lakehouse not working this morning

v-achippa — Wed, 22 Jan 2025 07:06:46 GMT

Hi @Amit_K,

Thank you for confirming that your issue has been resolved. I sincerely apologize for the inconvenience you experienced. Since you haven't encountered the issue since last Thursday, and the resolution is being gradually deployed across different regions. I request you to please accept this post as a solution to help other community members find it more quickly, and don't forget to give a Kudos – it would be greatly appreciated!

Thanks and regards,

Anjan Kumar Chippa

Re: GIT integration with Lakehouse not working this morning

datawithb — Wed, 22 Jan 2025 08:37:08 GMT

We have the same issue now in Sweden it seems, has anyone created a ticket regarding this i powerapps and got it resolved without waiting out 1 day?

Re: GIT integration with Lakehouse not working this morning

datawithb — Wed, 22 Jan 2025 10:31:26 GMT

@Amit_K

This issue pertains to the lakehouses in your repository. Although deleting the lakehouse, as only the metadata is version-controlled and resynchronized, temporarily resolves the problem, this is not an ideal solution. I have contacted the support team, but they have not provided an estimated time for a fix.

If you need a quick workaround for the moment, you can delete the lakehouse folder in your repository. Additionally, if you have any "Hidden" items, such as "StagingLakehouse," they should also be deleted. However, this should be done by someone familiar with navigating the Fabric environment, as it requires expertise to ensure everything integrates correctly. It is not recommended if you do not have oversight or control over how all components come together.