"juju metadata generate-image" does not validate architectures

Bug #1567747 reported by Andrew Wilkins on 2016-04-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned
juju-core
Undecided
Unassigned
1.25
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://pastebin.com/raw/kNXFnwLL

Naturally we won't find any images, because we look for "amd64". The command should have failed with a helpful message.

Curtis Hovey (sinzui) on 2016-04-12
tags: added: observability ui
Anastasia (anastasia-macmood) wrote :

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.

tags: added: simplestreams
Anastasia (anastasia-macmood) wrote :

This is related to https://bugs.launchpad.net/juju-core/+bug/1591488.

The underlying cause is the same.

Anastasia (anastasia-macmood) wrote :

@Andrew

Could you please provide the commands you've ran? pastebin has been removed ;(

I *think* this is fixed but I'd like to be sure \o/

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
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers