-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/mlflow] password authentication failed for user "bn_mlflow" when deploying with ArgoCD #28893
Comments
Hi! Could you confirm that you did not have leftovers from previous PostgreSQL PVCs? Maybe it is using a previous database password |
Cleared volumes, I will get back to you if the error persists. |
Hi! I'm also encountering the authentication error with MLflow and PostgreSQL. Has anyone else observed similar behavior or found a way to resolve this issue? Update: I've deployed it in a different namespace where there weren't any resources deployed and it worked (in case it helps someone else). |
@javsalgar issue still persists. I suspect this happened when we moved the MLFlow tracking pod to another node. |
Noticed this being the case in the Postgres pod. |
This seems to be caused by our ArgoCD based deployment for MLFlow. As a workaround, we're using:
|
(working with @lvijnck so adding more context) ArgoCD uses There unfortunately is no easy way to get the old passwords back it seems. Unless someone has a good idea how to get it from the rollback function of argocd |
The same this is true for Minio, where ArgoCD generates a new password on synchronisation breaking the Minio integration. We've followed the same steps above to mitigate for now. We're looking forward to see #28938 merged. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
@javsalgar I think it makes sense calling this out somewhere in the docs, as it's quite a nasty issue. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
mlflow 1.4.22
What architecture are you using?
amd64
What steps will reproduce the bug?
I've deployed MLFlow to my k8s cluster using ArgoCD, however after a while the MLFlow tracking container crashes due to unable to authenticate to PgSQL. This is with the default setup.
Are you using any custom parameters or values?
What is the expected behavior?
No crashing?
What do you see instead?
Crash
Tracking logs:
pgsql error:
Additional information
No response
The text was updated successfully, but these errors were encountered: