Looks like Juju isn't disambiguating enough in this case. Adding
"label=release" to the uvt-kvm call that Juju makes will probably fix
this specific case.
I'm not sure how best to manage the situation when the user can manually
pull in more images than Juju does. uvt-kvm currently requires that the
image be unambiguously specified. I wonder if there are other cases that
won't be covered?
Having said that, assuming that Juju still syncs only from the default
stream, adding a "label=release" shouldn't hurt anything and should fix
this.
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1317680
Title:
can't juju add machine when multiple images with same arch/release
exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1317680/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
