Juju fails to bootstrap on OpenStack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
nova (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I wan't create o juju controller on Openstack Cluod Canonical Queen version.
Error received:
- ERROR juju.cmd.
caused by: parse https:/
I have create a project and one VM and I have followed this documentation:
- https:/
- https:/
Following I give you all my step:
cat acilia_cloud.yaml
clouds:
acilia:
type: openstack
auth-types: [access-key, userpass]
regions:
RegionTwo:
endpoint: XXXXXXXXX
/opt/noemi# cat credentials.yaml
credentials:
acilia:
juju-
auth-type: userpass
project-
user-
tenant-name: canonicalk8s
username: XXXXXXXXX
password: XXXXXXXXX
$ juju add-cloud acilia acilia_cloud.yaml
$ juju add-credential acilia -f credentials.yaml --replace
$ juju show-cloud acilia
$ juju list-credentials --format yaml --show-secrets
$ juju metadata generate-image -d /opt/noemi/
$ juju bootstrap acilia canonicalk8s --config network=
b01c4b9e-
10:15:07 INFO juju.cmd supercommand.go:57 running juju [2.6.9 gc go1.10.4]
10:15:07 INFO cmd authkeys.go:114 Adding contents of "/root/
....
10:15:07 INFO juju.provider.
.....
10:15:08 ERROR juju.cmd.
caused by: parse https:/
10:15:08 DEBUG juju.cmd.
caused by: parse https:/
10:15:08 DEBUG juju.cmd.
10:15:08 INFO juju.provider.
10:15:08 INFO juju.provider.
10:15:08 ERROR juju.cmd.
caused by: parse https:/
10:15:08 INFO cmd supercommand.go:502 command finished
Changed in juju: | |
assignee: | nobody → Joseph Phillips (manadart) |
Changed in juju: | |
assignee: | Joseph Phillips (manadart) → nobody |
Changed in nova (Ubuntu): | |
status: | New → Incomplete |
Changed in juju: | |
status: | New → Triaged |
Thanks for the heads up on the issue. It looks like Juju is running across a space in trying to retrieve the flavor details. Somehow it's built the URL to get the file from as
"https:/ /computer2. cs1.cloudspc. it:8774, computer2. cs1.cloudspc. it:8774/ v2/" and it's not expecting to have the second bit of data there?
I'pm not sure if this is in the actual image metadata bit or in the config somewhere. Are you seeing those values in your setup?