Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Missing lakehouse/environment after deployment #944

Open
2 tasks
promisinganuj opened this issue Dec 11, 2024 · 0 comments
Open
2 tasks

[BUG] Missing lakehouse/environment after deployment #944

promisinganuj opened this issue Dec 11, 2024 · 0 comments
Assignees
Labels
blocked bug Something isn't working e2e: fabric Related with E2E Fabric Sample P0 Uber URGENT priority

Comments

@promisinganuj
Copy link
Contributor

There are several instances where the Fabric admin group members can't access Fabric Environment/Lakehouse after the initial deployment via SP. Here are some of the observations:

  • The items do get created successfully as verified by the terraform output and through the REST API calls.
  • The item access API doesn't work.
  • But I am able to confirm that my user has "Admin" role through an Entra security group, checked via Fabric Admin portal.
  • The issue happens randomly but often. It has been reproduced by at-least 4 people so far.
  • The issue happens on different tenants as well.

DoD

  • Investigate the root cause with the help of PG.
  • If required, implement a fix.
@promisinganuj promisinganuj added blocked e2e: fabric Related with E2E Fabric Sample bug Something isn't working P0 Uber URGENT priority labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked bug Something isn't working e2e: fabric Related with E2E Fabric Sample P0 Uber URGENT priority
Projects
None yet
Development

No branches or pull requests

3 participants