Closed Barteus closed 1 month ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5417.
This message was autogenerated
@paulomach agreed, my suspicion was that the metrics-endpoint-created
hook runs before the leader-elected
hook is run (thus the cluster-name
is unavailable in the app peer databag). since the hook errors out, the queued leader-elected
hook is never run
Workaround I found: First deploy without the cos overlay:
juju deploy --overlay auth-overlay.yaml --overlay mlflow-overlay.yaml --overlay storage-overlay.yaml ./kubeflow.yaml --trust -m kubeflow
And when everything settles deploy the overlay:
juju deploy --overlay auth-overlay.yaml --overlay cos-integration-overlay.yaml --overlay mlflow-overlay.yaml --overlay storage-overlay.yaml ./kubeflow.yaml --trust -m kubeflow
And the units come up fine
Steps to reproduce
Expected behavior
Deployment of Kubeflow works and Mysql-k8s charm provide the
Actual behavior
Versions
Operating system: Ubuntu 22.04.4 LTS
Juju CLI: 3.5.3
Juju agent: 3.5.3
Charm revision: 180
microk8s: 1.28
Log output
Juju debug log: log.txt
Additional context