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

Unable to delete a dashboard ( 3.0.0rc3) #25305

Closed
2 of 3 tasks
raghulprashath opened this issue Sep 14, 2023 · 1 comment · Fixed by #25320
Closed
2 of 3 tasks

Unable to delete a dashboard ( 3.0.0rc3) #25305

raghulprashath opened this issue Sep 14, 2023 · 1 comment · Fixed by #25320
Assignees

Comments

@raghulprashath
Copy link

Unable to delete a role-assigned dashboard in 3.0.0rc3

How to reproduce the bug

  1. Create a custom role with CRUD dashboard permissions.
  2. Make sure the DASHBOARD_RBAC feature is on.
  3. Create a dashboard and assign a role to the dashboard.
  4. Delete the dashboard - Throws error

Expected results

The dashboard is to be deleted

Actual results

This error is thrown:

sqlalchemy.exc.IntegrityError: (psycopg2.errors.ForeignKeyViolation) update or delete on table "dashboards" violates foreign key constraint "dashboard_roles_dashboard_id_fkey" on table "dashboard_roles" superset_app | DETAIL: Key (id)=(1) is still referenced from table "dashboard_roles".

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

  • browser type and version: Chrome (latest version)
  • superset version: 3.0.0rc3
  • python version: 3.9
  • node.js version: 16
  • any feature flags active: DASHBOARD_RBAC

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@john-bodley
Copy link
Member

@raghulprashath per my PR description I'm unsure as to why the referenced existing test didn't capture this. Would you mind manually testing my change to see if it remedies your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants