anuvdas opened a new issue, #44868:
URL: https://github.com/apache/superset/issues/44868
### Bug description
I upgraded the superset 6.0.0 instance to 6.1.0 and I encountered a BUG.
The bug is that..
1. You go to Settings-> List Roles
2. Try to edit any existing role like Gamma
3. You get an error "There was an error loading permissions."
4. After closing this error popup you go to Permissions and you see only
ids/number at the top.
5. You scroll up and down few times to see the associated permission names.
6. Role edit page triggers:
`/api/v1/security/permissions-resources/?q=(filters:!((col:id...`
7. API returns:
`{"message":"Filter column: id not allowed to filter"}`
Superset instance is deployed as a container in the Openshift/Kubernetes
Container Platform. Dockerfile was used to build the image and the stack
versions are given below.
```
Superset 6.1.0
Flask-AppBuilder 5.2.3
Python 3.12
```
`superset db upgrade` and `superset init` completed successfully. So I
believe there is no problem with backend PostgreSQL db, it is not corrupted.
Please let me know if you want to take a look at my Dockerfile,requirements.txt
or superset_config.py. I can upload them later.
Is there any way to fix this BUG or I need to wait for the next release ? I
see that the same issue is discussed in
[#41454](https://github.com/apache/superset/issues/41454) and
[#39967](https://github.com/apache/superset/issues/39967). However I am looking
for a solution especially for my Openshift deployment. I am not sure how to
apply the workaround that was suggested in those threads for my Openshift
container deployment.
### Screenshots/recordings
<img width="425" height="49" alt="Image"
src="https://github.com/user-attachments/assets/fbfc3de7-24b0-4c66-b144-bd47e3aa1703";
/>
https://github.com/user-attachments/assets/d56aff31-411f-4dea-9abb-5b0eb701c389
### Superset version
6.1.0
### Python version
3.12
### Node version
I don't know
### Browser
Firefox
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
