Comment 1 for bug 2048684

Revision history for this message
Joseph Phillips (manadart) wrote :

Based on your Discourse post, you have a connectivity issue to the resolved domain.

From https://discourse.charmhub.io/t/juju-controller-tries-for-non-existent-meta-data-url-to-pull-the-simplestream-json-file-failing-to-build-juju-machines-and-applications/12882/4:

 ERROR juju.worker.provisioner 29 cannot get available image metadata: failed getting published images metadata from default ubuntu cloud images: cannot read index data, attempt count exceeded: cannot access URL “http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson”: Get “http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson”: dial tcp 185.125.190.40:80: i/o timeout controller-0: 17:32:31 ERROR juju.worker.provisioner 30 cannot get available image metadata: failed getting published images metadata from default ubuntu cloud images: cannot read index data, attempt count exceeded: cannot access URL “http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson”: Get “http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson”: dial tcp 185.125.190.37:80: i/o timeout controller-0: 17:35:35

This shows the dial attempt failing and retrying, as opposed to getting a not found error, which would cause a fallback to reading index.sjson.

As far as I know, we've had no other reports of this issue.