cloudsigma index file has no data for cloud

[Aaron Bentley]

Note: We supplied tools-metadata-url, so juju should not be consulting cloudsigma storage for tools.

http://reports.vapour.ws/releases/2568/job/cloudsigma-deploy-trusty-amd64/attempt/34

All failures are reported at
    http://reports.vapour.ws/releases/issue/555e0d27749a566239dea515

[Aaron Bentley (abentley)]

A variation here: http://reports.vapour.ws/releases/2568/job/cloudsigma-deploy-trusty-amd64/attempt/33

This one lacks the "cannot start bootstrap instance:" text.

[Wayne Witzel III (wwitzel3)]

This was an issue with the index file on CloudSigma's end. It is fixed now. Please re-test.

[Aaron Bentley (abentley)]

Still a problem, though the message has changed slightly:
http://reports.vapour.ws/releases/2629/job/cloudsigma-deploy-trusty-amd64/attempt/49

[Wayne Witzel III (wwitzel3)]

ERROR juju.cmd supercommand.go:430 cannot set initial environ constraints: index file has no data for cloud {sjc https://sjc.cloudsigma.com/api/2.0/} not found

[Aaron Bentley (abentley)]

Latest example: http://reports.vapour.ws/releases/2707/job/cloudsigma-deploy-trusty-amd64/attempt/120

[Katherine Cox-Buday (cox-katherine-e)]

Per release planning, this will be targeted 1.24.1 if it cannot be fixed in the next 24h.

[Curtis Hovey (sinzui)]

Now that bug 1449208 is fixed, we can see that this bug is still happening
   http://reports.vapour.ws/releases/3055/job/cloudsigma-deploy-trusty-amd64/attempt/429

We have increase the retries to learn if this is an intermittent failure. We see it fail consistently

[Anastasia (anastasia-macmood)]

@Curtis - could we please re-try again with 1.25 tip? I have done a few changes in the area, especially how we are getting image metadata. At the very least, new run will give us better logs \o/ as I have also added more helpful logging \o/

[Anastasia (anastasia-macmood)]

It looks like we have stopped running CI against cloudsigma. I cannot find any latest cloudsigma tests.

Could you please either point me to the most recent related run or attach latest logs \o/

I suspect that this has been fixed.

[Anastasia (anastasia-macmood)]

These tests have not been run since October 2015. The issue is still there.

[Anastasia (anastasia-macmood)]

I am reducing this to Medium until we can get later CI runs or priority shifts.

[Anastasia (anastasia-macmood)]

As this is a tech-debt item, I am lowering its Importance.