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 sane archs for clouds. Previously it assumed the remote arch was the same as the local arch. I don't see much evidence of i386 being a sane selection for a cloud. The primary use of juju i386 is to provide a client that can work with amd64 clouds.
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 sane archs for clouds. Previously it assumed the remote arch was the same as the local arch. I don't see much evidence of i386 being a sane selection for a cloud. The primary use of juju i386 is to provide a client that can work with amd64 clouds.