You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a bug when upgrading Superset from 26.3 to nightly. Due to #722 we rotate the SECRET_KEY, resulting in
File "/stackable/app/lib64/python3.12/site-packages/sqlalchemy_utils/types/encrypted/encrypted_type.py", line 128, in decrypt
raise ValueError('Invalid decryption key')
Possible solution
I guess our operator should carry over the existing connections.secretKey or default to a random secret when creating the superset-secret-key Secret.
Workaround
If you want to temporarily work around it, put your old secretKey (in demos often supersetSecretKey) in the Secret superset-secret-key below SECRET_KEY. It will contain a random value which you override.
Activity
lfrancke commentedon Oct 20, 2026
Please add a release note snippet in the form "Previously, this went wrong. With this release, this was fixed in the following way."
sbernauer commentedon Oct 21, 2026
This was a fix for #722, which was also part of SDP 26.7. So it's release-internal, no need to have any release notes