diff --git a/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml b/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml index 37eddac1f5..21a53b4821 100644 --- a/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml +++ b/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml @@ -4,13 +4,13 @@ fixes: [`bug 1878938 `_] Previously when a user used to have system role assignment and tries to delete the same role, the system role assignments still existed in system_assignment - table. This fix ensures that deleting a role should delete all the its assignments - from every assignment table. + table. This causes keystone to return `HTTP 404 Not Found` errors when listing + role assignments with names (e.g., `--names` or `?include_names`). - If you are affected by this bug, a fix in the keystone database will be - needed so we recommend to remove the stale role assignmensts before doing this - process. + If you are affected by this bug, you must remove stale role assignments + manually. The following is an example SQL statement you can use to fix the + issue, but you should verify it's applicability to your deployment's SQL + implementation and version. SQL: - - delete from assignment where role_id not in (select id from role); - delete from system_assignment where role_id not in (select id from role);