Juju searches for index2.sjson in image streams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
When we bootstrap 2.0-beta1 we see that Juju is looking for an index file that image streams do not support. Only agent streams should look for index2.sjson. images streams look for index.sjson.
juju bootstrap curtis-beta1 aws --constraints mem=2G --config enable-
Creating Juju controller "curtis-beta1" on aws/us-west-1
ERROR streams/
ERROR streams/
Bootstrapping model "curtis-beta1"
ERROR streams/
ERROR streams/
Starting new instance for initial controller
Changed in juju-core: | |
milestone: | 2.0-beta2 → 2.0-beta3 |
Changed in juju-core: | |
milestone: | 2.0-beta3 → 2.0-beta4 |
tags: | added: 2.0-count |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0-rc1 |
milestone: | 2.0-rc1 → 2.0.0 |
tags: |
added: simplestreams removed: streams |
Changed in juju-core: | |
status: | Triaged → Incomplete |
milestone: | 2.0.0 → none |
affects: | juju-core → juju |
Changed in juju: | |
status: | Incomplete → Fix Released |
@Curtis - with all the latest changes in the area, is this still an issue on 2.0 tip?