Juju rc1 cannot deploy applications to openstack or centos

[Curtis Hovey]

As of
    http://reports.vapour.ws/releases/4386

Juju cannot deploy applications to openstack (canonistack and rackspace), nor can it deploy centos applications.

The only suspect revision is
https://github.com/juju/juju/commit/c46ddffc9c050a4404c31cae70cbf8ff53679fe2

[Christian Muirhead (2-xtian)]

Revert PR here: https://github.com/juju/juju/pull/6246

[Anastasia (anastasia-macmood)]

I've had a look at this failures and in all instances, images were found fine.

The problem is caused by something other than the commit specified. I'll re-instate it and will work with QA to find the actual issue.

[Anastasia (anastasia-macmood)]

Once my PR is applied, we take into account streams as specified in simplestreams.

Centos failed because product file https://streams.canonical.com/juju/images/releases/streams/v1/com.ubuntu.cloud.released-aws.sjson has a malformed content_id "content_id": "com.ubuntu.cloud.released:aws". It should be "com.ubuntu.cloud:released:aws" - notice colon not fullstop between "cloud" and "released". Colon is standard token separator.

I suspect similar issue for rackspace metadata but I cannot figure out how to access files used by rackspace tests.

[Anastasia (anastasia-macmood)]

For rackspace, tests seem to wantt o point to metadta location of http://5d117a7efe5779e2018e-77a1198a3891c2a6e76d39896aa23783.r47.cf1.rackcdn.com/images

But I cannot get to it, so I can't see what/if content id is defined on product file.

[Anastasia (anastasia-macmood)]

On further examination (thank you, mgz!), rackspace bootstrap for images metadata from http://5d117a7efe5779e2018e-77a1198a3891c2a6e76d39896aa23783.r47.cf1.rackcdn.com/images/streams/v1/com.ubuntu.cloud-released-imagemetadata.json needs to have image-stream config property to be set to "custom" as this is the stream value according to content_id.

[Curtis Hovey (sinzui)]

As we had just completed tests of the official rackspace product file. I copied it and the revised index.json to the image streams. These streams are "released" and they support all regions with precise, trusty, and xenial.

[Anastasia (anastasia-macmood)]

@Curtis
We pull content-id from product file not index file. We parse product file content_id - it's 2nd colon-separated token is stream. For example, content id: "com.ubuntu.cloud:released:aws"

[Anastasia (anastasia-macmood)]

I am reverting the change that caused these failures.