openstack havana bootstrap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
New
|
Undecided
|
Unassigned |
Bug Description
juju --version
1.16.5-
2013-12-11 16:57:52 DEBUG juju.environs.
2013-12-11 16:57:52 DEBUG juju.environs.
2013-12-11 16:57:52 DEBUG juju.environs.
2013-12-11 16:57:52 INFO juju.environs.
2013-12-11 16:57:52 DEBUG juju.environs.
caused by: Resource at http://
caused by: request (http://
2013-12-11 16:57:52 DEBUG juju.environs.
2013-12-11 16:57:52 DEBUG juju.environs.
caused by: Resource at http://
caused by: request (http://
2013-12-11 16:57:52 DEBUG juju.environs.
2013-12-11 16:57:53 DEBUG juju.environs.
2013-12-11 16:57:53 DEBUG juju.environs.
2013-12-11 16:57:53 DEBUG juju.environs.
2013-12-11 16:57:53 DEBUG juju.environs.
2013-12-11 16:57:53 ERROR juju supercommand.go:282 cannot start bootstrap instance: index file has no data for cloud {regionOne http://
Changed in juju-core: | |
status: | New → Incomplete |
Looks like Juju couldn't fix tools for the private cloud. Were tools published to a location in the private cloud? Does the tools-url in the config point to the tools path in the bucket's location.
eg. Did to select the tools collect the juju tools you want in the cloud and run juju sync-tools to places the tools in you private bucket, or did someone do the same to a public/shared bucket in the cloud?
I suspect that juju does work if you upload the tools while bootstrapping
juju bootstrap --upload-tools.