"juju metadata generate-image" does not validate architectures
Bug #1567747 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
| juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
| 1.25 |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Helping a user set up their private OpenStack, I directed him to the "juju metadata generate-image" command. He ran that, but passed "x86_64" for the architecture: http://
Naturally we won't find any images, because we look for "amd64". The command should have failed with a helpful message.
| tags: | added: observability ui |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| tags: | added: simplestreams |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #3 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
| milestone: | none → 2.0.1 |
| Changed in juju-core: | |
| status: | New → Won't Fix |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #4 |
| Changed in juju: | |
| importance: | High → Medium |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #5 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Yes, supported architectures needs to be adjusted to also pull architectures from metadata in state.
There was a plan to get metadata from both public sources and from state and return union of both set eliminating duplicates.