Closed dnegreira closed 6 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5457.
This message was autogenerated
Thanks for reporting this issue @dnegreira !
I tried reproducing it by deploying CKF 1.7 and upgrading to 1.8 following the upgrade guide. Is there an interim step you made for upgrading oidc
? Could you also share the output of juju status oidc-gatekeeper
? Are you upgrading to 1.8/stable?
Hi @DnPlas
juju status
:
ubuntu@kubeflow17:~$ juju status oidc-gatekeeper
Model Controller Cloud/Region Version SLA Timestamp
kubeflow uk8s34 my-k8s/localhost 2.9.46 unsupported 13:27:46Z
App Version Status Scale Charm Channel Rev Address Exposed Message
oidc-gatekeeper res:oci-image@7aae6d7 waiting 1 oidc-gatekeeper ckf-1.8/stable 350 10.152.183.192 no waiting for units to settle down
Unit Workload Agent Address Ports Message
oidc-gatekeeper/0* error idle 10.1.79.14 hook failed: "ingress-relation-changed"
The only interim step that I took are the ones in the guide: https://charmed-kubeflow.io/docs/upgrade-17-18#heading--upgrade-podspec-to-sidecar-charms
Are you upgrading to 1.8/stable?
Yes.
@dnegreira It seems like the version of juju you are using is still 2.9.x which may have a pebble version that is not yet compatible with the working-dir
field in the pebble layer. Could you please try migrating the agent version to 3.x and trying the refresh?
You could use this migration guide
hi @DnPlas
so I was missing the model-upgrade on the migration guide, which actually upgrades the model to the version of the new controller (which was already on the 3.1.7 version), and this issue is now solved.
Closing this issue as the error is related to an incompatible juju controller. Feel free to re-open if you run into the same issue.
Bug Description
When following the guide on the migration of kubeflow 1.7 to 1.8, the migration is finalized but there is an issue with the oidc-gatekeeper-operator charm is currently leaving the unit in error state.
To Reproduce
Follow the guide on a microk8s deployment and run a migration from juju 2.9 to 3.4.
Environment
Juju/Kubeflow on microk8s.
Relevant Log Output
Additional Context
No response