topic Re: Fabric - Missing attached lakehouse when deploying with deployment pipelines in Data Engineering

Fabric - Missing attached lakehouse when deploying with deployment pipelines

APG — Fri, 26 Jul 2024 10:13:21 GMT

Hi everyone,

I am currently working in a BI project based on Fabric. We are using notebooks to import, transform and refine data that will be later modeled in semantic models.

Our scenario:

we set up three workspaces (dev, test and prod)
dev workspace is connected to a git repository
we built a deployment pipeline to deploy notebooks from dev environment to test environment (and later to prod)
In dev environment each notebook has one lakehouse connected

Our issue:

when we deploy the notebooks to test environment, only a few of them are deployed with the lakehouse attached. All the other ones are deployed without any lakehouse attached; as a consequence we are not able to create deployment rules to switch default lakehouses from dev lakehouses to test lakehouses.

Regards,

APG

Re: Fabric - Missing attached lakehouse when deploying with deployment pipelines

Anonymous — Mon, 29 Jul 2024 03:06:54 GMT

Hi @APG ,

You can follow the steps below to troubleshoot and resolve the issue:

Ensure that Lakehouse is properly bound in the development and test environments. Sometimes the deployment pipeline may not recognise the Lakehouse as the same object if the Lakehouse is added after the initial workspace allocation .
Try unallocating and reassigning workspaces in the deployment pipeline. This will help ensure that the lake warehouse is correctly recognised as one object.

If the above steps do not help you resolve the issue, as a temporary solution you might need to manually attach the lakehouses in the test environment after deployment. It can help you move forward while the underlying issue is resolved.

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Fabric - Missing attached lakehouse when deploying with deployment pipelines

APG — Wed, 31 Jul 2024 08:24:39 GMT

Thank you for your reply; in my case none of the steps provided solved the issue.

After many checks on my notebooks I finally discovered that all the notebooks that "lost" the attached default lakehouse (during the deployment), had an empty cell at the end as a last cell.

Example:

Removing these last empty cells solved the issue: now all my notebooks are deployed with the default lakehouse attached.