Comment 22 for bug 1875481

It looks like the above error about jujud not being found is not the underlying cause of this issue. I tried deploying kubeflow with juju 2.8.1, and got the same behavior of getting errors about the unit not being a leader, without the error about jujud not being found.

It seems to be a flaky issue, as I was able to deploy kubeflow once successfully, but then wasn't able to a second time. The script broke due to juju-wait seeing a unit go into an error state, because of the error about not being a leader.

I'm able to reproduce this in CI, see here:

https://github.com/juju-solutions/bundle-kubeflow/pull/225/checks?check_run_id=870323388

Juju 2.8.1 errors out in those jobs due to this issue.