juju bootstrap fails on microk8s when microk8s is added with add-k8s

[Richard Harding]

Using the instructions here:
https://discourse.juju.is/t/using-juju-with-microk8s/1194

It fails to bootstrap if you use add-k8s as instructed and attempt to bootstrap to your new cloud. It hangs trying to connect to the IP of the controller pod.

16:47:32 INFO cmd controller.go:89 Contacting Juju controller at 10.152.183.215 to verify accessibility...
...

and then it fails and dies out.

[Tim McNamara (tim-clicks)]

That page only mentions add-k8s for Juju < 2.6. Are you using an old Juju
client?

On Wed, 27 May 2020 at 09:20, Richard Harding <email address hidden>
wrote:

> It fails to bootstrap if you use add-k8s as instructed and attempt to
> bootstrap to your new cloud. It hangs trying to connect to the IP of the
> controller pod.
>

[Richard Harding (rharding)]

No, this is the rc2 client. I think because of the fact that I had to run
the add group bits I didn't see the cloud after installing the snap. So I
went with the add-k8s path and that led me to this issue. I've gotten
around it after a reboot later on and bootstrapping to the built-in
microk8s cloud, but it seems this should work as well?

On Tue, May 26, 2020 at 5:30 PM Tim McNamara <email address hidden>
wrote:

> That page only mentions add-k8s for Juju < 2.6. Are you using an old Juju
> client?
>
> On Wed, 27 May 2020 at 09:20, Richard Harding <email address hidden>
> wrote:
>
> > It fails to bootstrap if you use add-k8s as instructed and attempt to
> > bootstrap to your new cloud. It hangs trying to connect to the IP of the
> > controller pod.
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880757
>
> Title:
> juju bootstrap fails on microk8s when microk8s is added with add-k8s
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1880757/+subscriptions
>

[Ian Booth (wallyworld)]

I tried to reproduce this

$ microk8s.config | juju add-k8s myk8s --client
k8s substrate "microk8s/localhost" added as cloud "myk8s".
You can now bootstrap to this cloud by running 'juju bootstrap myk8s'.

$ juju bootstrap myk8s
Creating Juju controller "myk8s-localhost" on myk8s/localhost
Creating k8s resources for controller "controller-myk8s-localhost"
Starting controller pod
Bootstrap agent now started
Contacting Juju controller at 10.152.183.179 to verify accessibility...

Bootstrap complete, controller "myk8s-localhost" is now available in namespace "controller-myk8s-localhost"

---

Could it be that a reboot was needed after freshly installing microk8s on a new machine?

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]