Unable to bootstrap with --metadata-source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Context:
From a "jumpserver" on a private openstack. I validate nova list etc.. works..
For 2.0 :
Tried:
$juju bootstrap openstack openstack --metadata-
2016-06-11 10:52:44 INFO juju.cmd supercommand.go:60 running juju [2.0-beta7 gc go1.6.1]
2016-06-11 10:52:44 DEBUG juju.cmd.
2016-06-11 10:52:44 INFO juju.provider.
2016-06-11 10:52:44 DEBUG juju.provider.
2016-06-11 10:52:44 INFO cmd cmd.go:129 Creating Juju controller "local.openstack" on openstack/RegionOne
2016-06-11 10:52:44 DEBUG juju.environs imagemetadata.
2016-06-11 10:52:44 DEBUG juju.environs imagemetadata.
2016-06-11 10:52:45 DEBUG juju.environs.
2016-06-11 10:52:45 INFO juju.provider.
2016-06-11 10:52:45 INFO juju.provider.
2016-06-11 10:52:45 DEBUG juju.provider.
2016-06-11 10:52:45 INFO juju.provider.
2016-06-11 10:52:45 DEBUG juju.provider.
2016-06-11 10:52:46 DEBUG juju.provider.
2016-06-11 10:52:47 ERROR cmd supercommand.go:448 index file has no data for cloud {RegionOne http://
I notice the same behavior with 1.25 ..
summary: |
- Can not bootstrap on private openstack juju 1.25 or 2.0 + remove deprecated option --metadata-source |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- remove deprecated option --metadata-source + Unable to bootstrap with --metadata-source |
Changed in juju-core: | |
importance: | Medium → High |
milestone: | none → 2.0-beta13 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
assignee: | nobody → Anastasia (anastasia-macmood) |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0-beta16 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta16 → none |
milestone: | none → 2.0-beta16 |
Changed in juju-core: | |
status: | New → Won't Fix |
Changed in juju-core: | |
status: | Fix Committed → Won't Fix |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
This looks a lot like bug #1452422 which claims to have been fixed already. Can you try to work around it by specifying image-metadata-url? (See comment #4 in that bug)