certificate signed by unknown authority
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
High
|
Unassigned |
Bug Description
tvansteenburgh@
ERROR Unable to connect to environment "local".
Please check your credentials or use 'juju bootstrap' to create a new environment.
Error details:
environment is not bootstrapped
tvansteenburgh@
total 8
drwxr-xr-x 2 root root 4096 Apr 7 00:26 ./
drwxr-xr-x 5 root root 4096 Mar 26 15:58 ../
tvansteenburgh@
NAME STATE IPV4 IPV6 AUTOSTART
-------
juju-precise-
juju-trusty-
tvansteenburgh@
uploading tools for series [trusty precise]
Logging to /home/tvansteen
Starting MongoDB server (juju-db-
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-
tvansteenburgh@
ERROR state/api: websocket.Dial wss://10.
ERROR state/api: websocket.Dial wss://10.
ERROR state/api: websocket.Dial wss://10.
^C2 tvansteenburgh@
1.17.7-trusty-amd64
tags: | added: local-provider ppc64el |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.19.0 |
Changed in juju-core: | |
milestone: | 1.19.0 → 1.19.1 |
New info on this. I was able to reproduce this repeatedly, destroying the environment, rebootstrapping, and getting this error when I'd run `juju status`. While asking for help in #IRC, it was suggested that I run bootstrap with the `--debug` flag and paste the resulting output. After doing so, the error no longer occurred (`juju status` returned normally and I was able to subsequently deploy a workload using the local provider). In case it helps, here's the output of that `juju bootstrap --debug` run: http:// pastebin. ubuntu. com/7217166/