`juju clouds` fails with `ERROR cmd: error out silently` when it cannot reach the controller in a Kubernetes cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
How to reproduce:
1. Get a K8S cluster up and running, like Minikube.
2. Bootstrap juju there.
3. Delete the cluster.
4. Get a new cluster, Minikube or any other platform.
Juju commands start to fail:
```
$ juju clouds
WARNING starting proxy for api connection: Get "https:/
ERROR cmd: error out silently
```
```
$ juju status
ERROR starting proxy for api connection: Get "https:/
```
Fixed by unregistering the controller:
```
$ juju unregister my-k8s-localhost
```
```
$ juju version
2.9-rc6-
```
summary: |
- `juju clouds` fails with `ERROR cmd: error out silently` when it can + `juju clouds` fails with `ERROR cmd: error out silently` when it cannot reach the controller in a Kubernetes cluster |
Clouds can be registered on your client and/or a controller, so the command attempts to access the current controller.
We could conceivably enhance this experience to write the clouds that can be gleaned from the client to stdout and print the controller access error to stderr...