cloudsigma index file has no data for cloud

Bug #1449210 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Low
Unassigned
juju-core
1.25
Won't Fix
Undecided
Unassigned

Bug Description

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)
summary: - juju.cmd supercommand.go:430 failed to bootstrap environment: cannot
- start bootstrap instance: index file has no data for cloud {sjc
- https://sjc.cloudsigma.com/api/2.0/} not found
+ cloudsigma index file has no data for cloud
Revision history for this message
Aaron Bentley (abentley) wrote :

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.

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.24-alpha1 → 1.24.0
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.24.0 → 1.25.0
Revision history for this message
Wayne Witzel III (wwitzel3) wrote :

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

Changed in juju-core:
assignee: nobody → Wayne Witzel III (wwitzel3)
status: Triaged → Fix Released
status: Fix Released → Fix Committed
Revision history for this message
Aaron Bentley (abentley) wrote :

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

Revision history for this message
Wayne Witzel III (wwitzel3) wrote :

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

Changed in juju-core:
assignee: Wayne Witzel III (wwitzel3) → Sergey Matyukevich (s-matyukevich)
Curtis Hovey (sinzui)
tags: added: tech-debt
Revision history for this message
Aaron Bentley (abentley) wrote :
Revision history for this message
Katherine Cox-Buday (cox-katherine-e) wrote :

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

Martin Packman (gz)
information type: Private → Public
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Released → Triaged
milestone: 1.25-alpha1 → 1.25-beta1
no longer affects: juju-core/db-log
no longer affects: juju-core/1.24
Revision history for this message
Curtis Hovey (sinzui) wrote :

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

Changed in juju-core:
milestone: 1.25-beta1 → 1.25-beta2
Curtis Hovey (sinzui)
description: updated
Changed in juju-core:
milestone: 1.25-beta2 → 1.25.1
Changed in juju-core:
milestone: 1.25.1 → 1.25.2
Changed in juju-core:
milestone: 1.25.2 → 1.25.3
Changed in juju-core:
milestone: 1.25.3 → 1.25.4
Changed in juju-core:
milestone: 1.25.4 → 1.25.5
Changed in juju-core:
milestone: 1.25.5 → 1.25.6
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@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/

tags: added: simplestreams
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.25.6 → 1.25.7
Revision history for this message
Anastasia (anastasia-macmood) wrote :

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.

Changed in juju-core:
status: Triaged → Incomplete
assignee: Sergey Matyukevich (s-matyukevich) → nobody
milestone: 1.25.7 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

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

no longer affects: juju-core
Changed in juju:
status: New → Won't Fix
status: Won't Fix → Triaged
importance: Undecided → High
milestone: none → 2.1.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

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

Changed in juju:
importance: High → Medium
milestone: 2.1.0 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

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

Changed in juju:
importance: Medium → Low
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.