Closed ACodingfreak closed 16 hours ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5913.
This message was autogenerated
I run into the same issue and was able to resolve it by using Juju 3.4. After getting the same error, I run these steps to install Juju 3.4 and remove the controller and models created with Juju 3.1
Update to Juju 3.4
sudo snap refresh juju --channel 3.4/stable
Remove the old model and controller
juju destroy-model --destroy-storage --force kubeflow
juju destroy-controller --destroy-storage --force uk8sx
And then deploy the Juju controller and add the model again
juju bootstrap my-k8s uk8sx
juju add-model kubeflow
And finally, deploy kubeflow again
juju deploy kubeflow --trust --channel=1.8/stable
I wasn't able to get this working with Juju 3.5 due to a similar error
Thanks for the reply @brianmusisi
I did try the same with Juju 3.4 microk8s 1.29 CKF 1.8 and ended up with katib-db-manager issue
Hey, thank you for reporting this. Juju 3.1 is not supported anymore but we had not updated the documentation. We just did that prompting everyone to use Juju 3.4 (supported versions, get started guide). Closing this issue.
Bug Description
As shown in below logs on deploying 1.8/stable kubeflow from Juju 3.1 fails because of dependency issues of katib-db. I am just following the instructions suggested by canonical in below article
https://charmed-kubeflow.io/docs/get-started-with-charmed-kubeflow
To Reproduce
Follow the instructions in below article
https://charmed-kubeflow.io/docs/get-started-with-charmed-kubeflow
Environment
Ubuntu 22.04 microk8s 1.29/stable juju 3.1/stable kubeflow 1.8/stable
Relevant Log Output