resolv.conf in cloud-images should be empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on EC2 |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
In the image build process, resolv.conf gets populated from the build system's /etc/resolv.conf.
This is somewhat of a requirement, but the problem is that it is being left there for older releases.
I just went through all the release images on cloud-images.
* 8.04 hardy: puppet
* 10.04 lucid: puppet
* 10.10 maverick: puppet
* 11.04 natty: puppet
* 11.10 oneiric: empty, zero length regular file
* 12.04 precise: dangling symlink to ../run/
* 12.10 quantal: dangling symlink to ../run/
For reference, the 'puppet' config that I see in the most recent images has a 'puppet' ascii art heading, and then says:
| # This file is managed by puppet. Do not make local changes.
|
| search canonical.com ubuntu.com
| nameserver 91.189.94.2
| nameserver 91.189.94.3
This file should probably be empty by default, and rely entirely on dns provided by dhcp configuration of eth0.
Changed in ubuntu: | |
status: | Triaged → Fix Released |
no longer affects: | Ubuntu Natty |
no longer affects: | Ubuntu Lucid |
no longer affects: | Ubuntu Hardy |
affects: | ubuntu → ubuntu-on-ec2 |
Changed in ubuntu-on-ec2: | |
milestone: | ubuntu-12.10-beta-1 → none |
for 12.04 and 12.10, the dangling symlink _is_ proper. This enables the use of resolvconf. At boot time, resolvconf will populate /run/resolvconf /resolv. conf. Removal of this symlink causes Bug 1003595.
For 8.04 through 11.10, they should be deleted. I'lll work on this and release new images. 8.04 is over due for a refresh itself.
Looking at the actual EC2 instances, this only affects the images, not the images pushed to EC2.