Rackspace no longer works with Juju

[Curtis Hovey]

Rackspace cloud has changed. No version of juju can bootstrap. Juju or Rackspace needs to change to allow users to bootstrap.
As seen in
    http://reports.vapour.ws/releases/issue/56eaba9f749a56698ae41fa2

The devel jujus cannot bootstrap. Juju CI's cloud health checks that use a stable (ish) juju shows that even a reliable juju cannot bootstrap. The last successful bootstrap was at 05-May-2016 08:46:25 UTC.

the error is consistently like this
    index file has no data for cloud {DFW https://identity.api.rackspacecloud.com/v2.0} not found

[Anastasia (anastasia-macmood)]

The most recent change in the area was to do with region name cases.

@Curtis - could we bootstrap rackspace with these changes? If yes, have rackspace images changed lately?

[Curtis Hovey (sinzui)]

@Anastasia Since NO version of juju can bootstrap going all the way back 1.26-alpha1 and the cloud health checks use an older Juju. I am sure Juju has not changed anything. Streams may have changed, or the cloud has changed.

[Curtis Hovey (sinzui)]

Sourcing the rackspace OpenStack creds, I can run 'nova' to boot an image using the same account and keys used by cloud health checks and revision tests.

[Eric Snow (ericsnowcurrently)]

Per Martin, this is not an issue in core.

[Cheryl Jennings (cherylj)]

I was able to bootstrap yesterday in DFW with the following config:

image-metadata-url: http://0315ec36e423bb7dba4b-3eabf88619cf7b7e6fc262bcf48df10b.r19.cf1.rackcdn.com/images
image-stream: "released"

[Curtis Hovey (sinzui)]

This issue is resolved, but I am concerned this issue can happen again.

1. Canonical, and specifically CPC does not provide official Ubuntu images to rackspace. You wont find rackspace in image streams at cloud-images.ubuntu.com.

2. Martin generated streams to test the the rackspace provder works. These streams have become the defacto official streams. see
   https://jujucharms.com/docs/master/help-rackspace

3. Both CPC and Juju QA share the account to test in rackspace. The rackspace streams are just files in swift under the shared account.

4. There was a cleanup of resources in that account a just prior to the outage. Someone not realising the swift container serves images streams deleted it.

The images streams were republished. It took just a few minutes.

Until CPC provides official images and streams, we need to safeguard the streams in the shared account.

1. The cloud health check was successful in identifying the issue. Now that we understand it, it is easy to take immediate action to republish streams to the swift container.

2. We cannot lock the container. So the CPC and juju QA team need to know NEVER delete juju-ci-image-streams container or its objects.