juju bootstrap lxd should not care about microk8s
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Undecided
|
Unassigned | ||
2.9 |
Triaged
|
Undecided
|
Unassigned |
Bug Description
On a fresh vm, I was getting ready to test some things, and I did:
$ sudo snap install microk8s --classic
$ juju bootstrap lxd lxd
ERROR Insufficient permissions to access MicroK8s.
You can either try again with sudo or add the user jameinel to the 'microk8s' group:
sudo usermod -a -G microk8s jameinel
sudo chown -R jameinel ~/.kube
After this, reload the user groups either via a reboot or by running 'newgrp microk8s'.
Note that I'm bootstrapping lxd (not microk8s), but the fact that I cannot read the microk8s socket is causing it to fail.
I'm guessing we have a probe around 'what clouds do we have', and if the microk8s socket isn't there, we just skip it, but if it is there we query it. But if the query fails, it should just say that we don't have microk8s, not block other clouds from working.
This was done with 2.9.38 from the juju snap. (This does not happen with the strictly confined juju 3.0 snap.)
Marking this as Fixed for mainline juju, but broken in 2.9