Microsoft Fabric DevOps Sync Issue: Lakehouses Not Fully Syncing

[goldenarm253]

Hi Community,

I'm encountering an issue with Microsoft Fabric where not all lakehouses are syncing correctly via DevOps. While notebooks, pipelines, and warehouses are syncing without issue, only one lakehouse has successfully synced, and the others fail. Below are the details of the error:

• Error Message:
  • "Something went wrong"
• Details:
  • Cluster URI: https://wabi-us-north-central-b-redirect.analysis.windows.net/
  • Request ID: 00000000-0000-0000-0000-000000000000
  • Time: Thu Jan 16, 2025, 13:00:49 GMT-0500 (Eastern Standard Time)

Observations:

• Notebooks, pipelines, and warehouses sync successfully.
• Only one lakehouse synced successfully; others failed repeatedly.
• I've verified the configurations but can't pinpoint the issue.

Questions:

1. Is this a configuration or compatibility issue in DevOps specific to lakehouses?
2. Are there regional limitations or known bugs with lakehouse syncing in the North Central US cluster?
3. What additional logs or diagnostic steps could help identify the cause?

Any guidance or suggestions for troubleshooting would be greatly appreciated!

[v-csrikanth]

Hi @goldenarm253 
Here are some troubleshooting steps to resolve your issue.

1. Verify Lakehouse-Specific Configurations:

• Double-check the configurations for each lakehouse in the DevOps pipeline and ensure they match the one that synced successfully.
• Confirm that all lakehouses are using the same version of the pipeline scripts and have the same dependencies configured.

2. Check Cluster and Region Status:

• Visit the Azure Status page to check if there are any ongoing issues in the North Central US region: Azure Status.

3. Examine Error Logs in Detail:

• While the error message in your post is generic, additional logs may provide more insights. Here’s where you can look:
  • Fabric Logs: Check the activity logs for detailed information on the failed sync operations.
  • DevOps Logs: Review the pipeline logs for errors or warnings related to lakehouse resources.
  • Lakehouse Logs: If accessible, look into the diagnostic logs for the lakehouses that failed to sync.

4. Test with Manual Sync:

• Try manually syncing the lakehouses that failed via the Microsoft Fabric UI to see if the error persists. This can help determine whether the issue lies with the DevOps pipeline or the lakehouse resource itself.

5. Check Resource Limits:

• Validate your subscription's resource limits for lakehouses in Microsoft Fabric. Exceeding limits may result in some lakehouses failing to sync:
  • Tenant-wide lakehouse limits
  • Storage or compute capacity for the region

6. Recreate the Failing Lakehouses:

• Export the configurations of the failing lakehouses.
• Delete and recreate the lakehouses, then attempt to sync again. This can resolve issues related to metadata corruption.

If the above information helps you, please give us a Kudos.

Thanks,
Cheri Srikanth

[goldenarm253 · Accepted solution]

After waiting for three days sync finally worked.