| 2012-07-05 17:19:24 |
David Britton |
description |
cloud-init seems to attempt to detect ubuntu-mirror.localdomain (if you don't have a real domain setup), and does so by resolving the name. It should probably go a step further than this since some ISPs (mine for instance) redirect invalid requests to a search page or something else. Maybe downloading the dists/${CODENAME}/Release.gpg file or something like that.
The result of this is cloud init thinks there is a valid mirror at ubuntu-mirror.localdomain, and apt gets confused as files seem to download, but they are meaningless html content from whatever search site they are redirecting me to.
This is coming into play with a kvm precise instance initialized with cloud-init. |
cloud-init seems to attempt to detect ubuntu-mirror.localdomain (if you don't have a real domain setup), and does so by resolving the name. It should probably go a step further than this since some ISPs (mine for instance) redirect invalid requests to a search page or something else. Maybe downloading the dists/${CODENAME}/Release.gpg file or something like that.
The result of this is cloud init thinks there is a valid mirror at ubuntu-mirror.localdomain, and apt gets confused as files seem to download, but they are meaningless html content from whatever search site they are redirecting me to.
This is coming into play with a kvm precise instance initialized with cloud-init.
I've changed my router to use Google's public DNS servers and have worked around the problem, but just reporting this so that others may be able to be helped. |
|
