GIT integration with Lakehouse not working this morning

[Amit_K]

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.

AK

[afraaij_Amphia]

Please confirm that this is not solved, the GIT Integration issue still exists.

[timahenning2]

Hi Anjan,

Is the service degradation posted on the Fabric service status? This would help avoid users looking for it in the community posts.

Tim 

[dnope]

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/features-samples/fabric-apis/LongRunningOperation-Polling.ps1 at main · microsoft/fab...

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>

[Amit_K]

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

[afraaij_Amphia]

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?

[BenjaminSchenk]

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

[v-achippa]

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

[afraaij_Amphia]

Still an issue, from 2025-01-22 we can not use source control any more in workspaces.
Giving a message like:

Disconnecting the workspace from GIT and reconnecting works until the sync is started and then this error occures.

[wiumjolene]

This issue is in South Africa North as well

[linsonabr]

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. 

[Sam_]

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.

[wiumjolene]

Any update?

[andresvargas99]

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?

[Amit_K]

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

[CJG2090]

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

[andresvargas99]

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

[Amit_K]

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

[Amit_K]

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.