-
Notifications
You must be signed in to change notification settings - Fork 47
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
katib-db-manager: waiting for relational-db data #961
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5950.
|
Hi @ACodingfreak thanks for reporting this! Please note there is a From the
As you mentioned, it is stuck in Pinging @paulomach, @shayancanonical - have you folks run into this? what other logs could be useful for debugging this issue? |
my guess is that there is some sort of pebble issue causing mysqld to not start up, followed by errors connecting to the mysqld service. would you have the relevant error traces from the mysql the following error occurs numerous times first:
after a while, the following error repeats in the logs
|
Hi All, I did attach logs from katib-db container in the bug named as mysql.zip. Is this good enough ? https://github.com/user-attachments/files/16057534/mysql.zip Sorry to say but as I need to quickly bring up CKF, I ended up downgrading the setup into microk8s:1.24 juju:2.9 kubeflow:1.7 Like microk8s inspect is there a command for juju to dump all the logs needed for troubleshooting ? |
Unfortunately, we dont yet have a tool similar to Were you able to get CKF running? If not, would you be able to provide us with the environment details where you're deploying CKF so we can reproduce the issue? |
@shayancanonical I think they did:
|
Bug Description
As shown in below logs, Katib-db-manager is continously waiting for the relation-db data from mysql which is still busy in installing the Agent
To Reproduce
Environment
Relevant Log Output
Logs from mysql katib-db container
mysql.zip
Additional Context
No response
The text was updated successfully, but these errors were encountered: