Juju searches for index2.sjson in image streams

[Curtis Hovey]

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-os-upgrade=false --bootstrap-series trusty
Creating Juju controller "curtis-beta1" on aws/us-west-1
ERROR streams/v1/index2.sjson not accessed, actual error: invalid URL "https://streams.canonical.com/juju/images/releases/streams/v1/index2.sjson" not found
ERROR streams/v1/index2.sjson not accessed, actual error: invalid URL "http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson" not found
Bootstrapping model "curtis-beta1"
ERROR streams/v1/index2.sjson not accessed, actual error: invalid URL "https://streams.canonical.com/juju/images/releases/streams/v1/index2.sjson" not found
ERROR streams/v1/index2.sjson not accessed, actual error: invalid URL "http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson" not found
Starting new instance for initial controller

[Anastasia (anastasia-macmood)]

@Curtis - with all the latest changes in the area, is this still an issue on 2.0 tip?