I would target this to a 1.18.2 if it existed.
This is a change in behavior from 1.16 to 1.18. If you just do:
juju-1.18 bootstrap -e amazon
I end up getting a i386 target. I have to do:
juju-1.18 bootstrap -e amazon --constraints=arch=amd64
for it to pick a amd64 (which was always the default
I would target this to a 1.18.2 if it existed.
This is a change in behavior from 1.16 to 1.18. If you just do:
juju-1.18 bootstrap -e amazon
I end up getting a i386 target. I have to do:
juju-1.18 bootstrap -e amazon --constraints=arch=amd64
for it to pick a amd64 (which was always the default
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: metadata
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I wonder if this is a bug in juju metadata. I noticed recently that when
I generate data for tools , 1.15.0 is always the version for amd64. I
think the version is selected from the oldest tool found for the
series+arch.
Metadata might be unrelated. Juju is trying to be smarter about
selecting
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: metadata
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
I wonder if this is a bug in juju metadata. I noticed recently that when
I generate data for tools , 1.15.0 is always the version for amd64. I
think the version is selected from the oldest tool found for the
series+arch.
Metadata might be unrelated. Juju is trying to be smarter about
selecting
