You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "suryansh-ksolves (via GitHub)" <gi...@apache.org> on 2024/12/16 05:03:30 UTC
[I] SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3 [superset]
suryansh-ksolves opened a new issue, #31461:
URL: https://github.com/apache/superset/issues/31461
### Bug description
I recently upgraded Superset to version 2.x.x to Version 3.1.3, including updating the Superset image and database. After the upgrade, I am unable to open SQL Lab, receiving an error displayed in a screenshot. Additionally, I encounter an "Access Denied" error when trying to open Row-Level Security.
Could someone suggest a solution for these issues?
### Screenshots/recordings
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### 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.
- [ ] 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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #31461:
URL: https://github.com/apache/superset/issues/31461#issuecomment-2544607282
<!-- Greeting -->
@suryansh-ksolves Hello there! I'm here to help you with the SQL Lab issue and the "Access Denied" error you've encountered after upgrading to version 3.1.3. I'm a bot designed to assist you with bug resolution, answer your questions, and guide you to become a contributor. Let's work together to solve these issues!
<!-- Answer -->
To resolve the "Unexpected error" and "Access Denied" issues in SQL Lab and Row-Level Security after upgrading Apache Superset from version 2.x.x to 3.1.3, you should address the permission naming inconsistency. Specifically, manually update the permission name from 'Sqllab' to 'SQLLab' in the database. This inconsistency is due to a permission renaming that occurred without a corresponding database migration. The codebase uses a mix of 'SQLLab' and 'SQL Lab', which can lead to these issues. This manual update is a temporary workaround until a proper migration is implemented, potentially in version 5.0 <sup>[[1]](https://github.com/apache/superset/issues/31395)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/ef3cf98d-8e45-452c-b1c6-1698faa124c7?feedback_type=other)</sup>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3 [superset]
Posted by "suryansh-ksolves (via GitHub)" <gi...@apache.org>.
suryansh-ksolves commented on issue #31461:
URL: https://github.com/apache/superset/issues/31461#issuecomment-2544654645
How can I fix this in our current Environment?
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3 [superset]
Posted by "suryansh-ksolves (via GitHub)" <gi...@apache.org>.
suryansh-ksolves closed issue #31461: SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3
URL: https://github.com/apache/superset/issues/31461
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] SQL Lab Issue after upgrade the Imange from version 2.x.x to version 3.1.3 [superset]
Posted by "suryansh-ksolves (via GitHub)" <gi...@apache.org>.
suryansh-ksolves commented on issue #31461:
URL: https://github.com/apache/superset/issues/31461#issuecomment-2544710346
The issue has been resolved in my environment. To upgrade Superset with a new image, I first deploy the new image, then run the command superset db upgrade inside the Superset pod, followed by superset init.
Please refer to the above ticket for details about the reported issue:
https://github.com/apache/superset/issues/29482
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org