Azure provider: Juju unable to locate any image when "image-stream: released" is set (doesn't validate content of image-stream)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Low
|
Unassigned |
Bug Description
Using:
juju --version
1.13.3-
and setting the following for my azure config in environments.yaml:
image-stream: released
default-series: precise
From what I can tell Juju is parsing the released simple stream data incorrectly:
2013-08-31 00:07:55 DEBUG juju.environs.
2013-08-31 00:07:55 DEBUG juju.environs.
2013-08-31 00:08:12 ERROR juju supercommand.go:282 command failed: cannot start bootstrap instance: no OS images found for location "West US", series "precise", architectures ["amd64" "i386"] (and endpoint: "https:/
Juju is looking in:
http://
for
"com.
Juju should be looking for:
com.
Note the com.ubuntu.
daily = com.ubuntu.
released = com.ubuntu.
This is why daily streams bootstrap:
image-stream: released
default-series: precise
I think Juju just needs to update is parsing to drop the ".released" in the com.ubuntu.com simple stream parsing.
Changed in juju-core: | |
status: | New → Triaged |
Changed in juju-core: | |
milestone: | 1.15.0 → 1.16.0 |
tags: | added: azure |
Changed in juju-core: | |
importance: | High → Critical |
assignee: | nobody → John A Meinel (jameinel) |
tags: |
added: azure-provider removed: azure |
It is important to use "released" streams as there is no warranty or QA on daily images.