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
trying to reset the password but getting below error
{"code":2,"message":"unable to generate recovery url"}
Steps to reproduce the bug
Fresh install using quick start guide
click reset password of admin user
Are you using the latest version of the project?
You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.
❯ helm ls -A
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
myrelease paralus 1 2024-07-22 13:06:01.588546 +0200 CEST deployed ztka-0.2.9 v0.2.8
What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
[x ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
[ x] I'm using the latest version of the project.
The text was updated successfully, but these errors were encountered:
Expected vs actual behavior
trying to reset the password but getting below error
{"code":2,"message":"unable to generate recovery url"}
Steps to reproduce the bug
Are you using the latest version of the project?
You can check your version by running
helm ls|grep '^<deployment-name>'
or using pctl,pctl version
, and provide the output.What is your environment setup? Please tell us your cloud provider, operating system, and include the output of
kubectl version --output=yaml
andhelm version
. Any other information that you have, eg. logs and custom values, is highly appreciated!(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
The text was updated successfully, but these errors were encountered: