I am not sure how to access them on ubuntu support server. If these logs do not have any private info, they could be attached here.
And also, another question....
Juju caches images on the controller to minimise image downloads and, hence, traffic, to enable consistent deployment of several units. We cache them but we expire them after 5 mins. This means that if there are cached images that match your requirements, we will not re-download them even if you update image-metadata-url (maybe we should rect to that change in the future but, at the moment, we do not track where the images came from and to react to image-metadata-url changes, we'd need to do that).
So, the question is... Has 5 mins passed since the last time a deployment/machine provisioning happenned? I believe that if there are no cached images, we'd try the image-metadata-url... One way to know would be to change image-metadata-url and try deployment after 6+ mins... :D
@Ed Stewart (emcs2),
I am not sure how to access them on ubuntu support server. If these logs do not have any private info, they could be attached here.
And also, another question....
Juju caches images on the controller to minimise image downloads and, hence, traffic, to enable consistent deployment of several units. We cache them but we expire them after 5 mins. This means that if there are cached images that match your requirements, we will not re-download them even if you update image-metadata-url (maybe we should rect to that change in the future but, at the moment, we do not track where the images came from and to react to image-metadata-url changes, we'd need to do that). url... One way to know would be to change image-metadata-url and try deployment after 6+ mins... :D
So, the question is... Has 5 mins passed since the last time a deployment/machine provisioning happenned? I believe that if there are no cached images, we'd try the image-metadata-