Katib-db stuck at login as root
See original GitHub issue/kind bug
What steps did you take and what happened: [A clear and concise description of what the bug is.] I try to deploy Katib on IBM Cloud and use IBM Cloud NFS storage as the persistent volume. However, the Katib-db always stuck at
2019-08-15T17:57:04.708439Z 35240 [Note] Access denied for user 'root'@'localhost' (using password: YES)
2019-08-15T17:57:06.771754Z 35241 [Note] Access denied for user 'root'@'localhost' (using password: YES)
2019-08-15T17:57:08.713518Z 35242 [Note] Access denied for user 'root'@'localhost' (using password: YES)
One thing I do realize is our persistent storage doesn’t allow nonroot user to write files. Although the deployment is working if we try to use hostpath, it won’t be persistent and resilient in our use case.
We also try our storage with the KubeFlow Pipeline MySQL and it works fine there. The only different is KubeFlow Pipeline doesn’t have any password for its MySQL instance.
What did you expect to happen: Katib-db should be deployed and login as root.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- Kubeflow version: 0.5.1 and 0.6.0
- Minikube version:
- Kubernetes version: (use
kubectl version
): 1.14.5 - OS (e.g. from
/etc/os-release
): ubuntu 16
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top GitHub Comments
Thanks @gaocegege, we removed the root password for the katib-db and it’s able to run now. However, the katib-manager always fallbacks the password to
test
when the password is set to empty which makes it cannot login to the katib-db. Is there a way to let katib-manager login with empty password without changing the source-code?https://github.com/kubeflow/katib/blob/2d059a44d85f9a70a090b8bd3f86c22f5aef4048/pkg/db/v1alpha2/interface.go#L72-L83
@hougangliu: Closing this issue.
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.