vsphere: new architectures updates are not picked by running environments

[Anastasia]

From Juju 2.0, most providers that use simplestreams can pick up new architectures as soon as their images become available. This enables users to start new machines using these newer images by specifying their architectures as part of the desired constraints.

We cannot do this on VSphere as supported architectures are cached at bootstrap time. If new images become available, provider can use them. However, if new images are for the new architectures, constraints that try to specify these architectures will not be considered valid.

This is easily fixed by not caching supported architectures. We need to ensure that removing caching is not significantly degrading performance.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.