Comment 15 for bug 2032783

Alright, I'm one step further after purging everything again. The sunbeam bootstrap still doesn't finish (at least not within an hour or so), and I do see a prompt asking for proxy settings. But when I run the 'juju bootstrap sunbeam sunbeam-controller ...' first, I get a little more progress with the sunbeam bootstrap command:

ubuntu@sunbeam:~$ sunbeam cluster bootstrap -m /snap/openstack/current/etc/manifests/edge.ymlConfigure proxy for access to external network resources? [y/n] (y): y
Enter value for http_proxy: (http://IP:PORT): http://IP:PORT
Enter value for https_proxy: (http://IP:PORT): http://IP:PORT
Enter value for no_proxy: (localhost, 172.17.2.0/24): localhost, 172.17.2.0/24
Management networks shared by hosts (CIDRs, separated by comma) (172.17.2.0/24): 172.17.2.0/24
MetalLB address allocation range (supports multiple ranges, comma separated) (10.20.21.10-10.20.21.20): 10.20.21.10-10.20.21.20

But now it seems to be stuck here:
⠏ Adding MicroK8S unit to machine ...

In the syslog I see a lot of these messages:

Apr 24 07:38:25 sunbeam microk8s.daemon-kubelite[9327]: E0424 07:38:25.318497 9327 kubelet.go:2855] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"

But it's still running, so I'll wait for the result. But regarding proxy settings, I still don't think it works as expected, given that I have to run the juju command separately.