juju bootstrap with local lxd failed with "x509: certificate is valid for *, not VCA"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Undecided
|
Unassigned |
Bug Description
juju version: 2.0.2-xenial-amd64
lxd version: 2.0.10
OS version: ubuntu 16.04 LTS amd64 (release) (20170619.1)
I'm in process of installing etsi OSM Release TWO on a VM hosted in a corporate Openstack cloud. The installation is success, but the juju server which supposed to be configured successfully on VCA is not configured. I have to login to the VCA lxd container hosted on the OSM VM to run juju bootstrap manually with following command:
$ juju bootstrap -v --debug --show-log --config=
Content of config.yaml is nothing but corporate proxy settings, e.g. apt-http-proxy. It always failed with following error: (10.44.127.1 is IP address of lxdbr0 on VCA)
2017-07-22 08:37:06 INFO juju.cmd supercommand.go:63 running jujud [2.0.2 gc go1.6.2]
2017-07-22 08:37:06 DEBUG juju.cmd supercommand.go:64 args: []string{
2017-07-22 08:37:06 DEBUG juju.agent agent.go:509 read agent config, format "2.0"
2017-07-22 08:37:06 DEBUG juju.tools.
2017-07-22 08:37:57 ERROR cmd supercommand.go:458 new environ: creating LXD client: Get https:/
2017-07-22 08:37:57 DEBUG cmd supercommand.go:459 (error details: [{github.
2017-07-22 08:37:57 DEBUG juju.cmd.jujud main.go:163 jujud complete, code 0, err <nil>
Verified lxd is listening on 8443 port:
root@VCA:~# curl -k https:/
{"type"
I'm also reading this bug: https:/
Changed in juju: | |
status: | New → Invalid |
Content of config.yaml for reference:
default-series: xenial
no-proxy: localhost
apt-http-proxy: <proxy url>
apt-https-proxy: <proxy url>
apt-ftp-proxy: <proxy url>
http-proxy: <proxy url>
https-proxy: <proxy url>
ftp-proxy: <proxy url>