Following an ad-hoc troubleshooting session on #juju. So far it seems the easiest workaround is to add these lines in the generated environments.yaml:
(for 1.20x) tools-metadata-url: https://streams.canonical.com/juju/tools image-metadata-url: http://cloud-images.ubuntu.com/releases
(for 1.21+) agent-metadata-url: https://streams.canonical.com/juju/tools image-metadata-url: http://cloud-images.ubuntu.com/releases
Then quickstart can run $ juju metadata validate-tools and $ juju metadata validate-images to ensure those will work before attempting to bootstrap.
Following an ad-hoc troubleshooting session on #juju. So far it seems the easiest workaround is to add these lines in the generated environments.yaml:
(for 1.20x) /streams. canonical. com/juju/ tools cloud-images. ubuntu. com/releases
tools-metadata-url: https:/
image-metadata-url: http://
(for 1.21+) /streams. canonical. com/juju/ tools cloud-images. ubuntu. com/releases
agent-metadata-url: https:/
image-metadata-url: http://
Then quickstart can run $ juju metadata validate-tools and $ juju metadata validate-images to ensure those will work before attempting to bootstrap.