New resolvconf interacts badly with something in installs
Bug #926447 reported by
Thomas Bushnell, BSG
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netcfg (Ubuntu) |
Fix Released
|
Critical
|
Stéphane Graber | ||
Bug Description
As of ubuntu7 (and maybe ubuntu6), we get failing installs related to the new resolvconf changes which do the /etc/resolv.conf link in the postinst.
During the "select and install software" step, we see /etc/resolv.conf go away (simply vanish) at some point in the prep step, and then we get the question about automatic upgrades, and then it goes away again during the install packages step. Then when the resulting error is printed (that it can't find our package source or proxy, because the names don't resolve) it gets put back.
It's really clear what's happening when I have another VT which just does ls -l /etc/resolv.conf in a loop.
Still investigating.
Revision history for this message
| Stéphane Graber (stgraber) wrote | #1 |
| Changed in resolvconf (Ubuntu): | |
| importance: | Undecided → Critical |
| assignee: | nobody → Stéphane Graber (stgraber) |
| affects: | resolvconf (Ubuntu) → netcfg (Ubuntu) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in netcfg (Ubuntu): | |
| status: | New → Fix Released |
Revision history for this message
| Thomas Bushnell, BSG (tbushnell) wrote | #3 |
To post a comment you must log in.
I can confirm it here so marking as Critical but not marking as Triaged just yet as I'm unsure it's resolvconf's fault.
It may instead be netcfg's or another d-i component touching /etc/resolv.conf
Resolvconf's behavior at install time is:
- Move current resolv.conf to /run/resolvconf
- Make relative symlink from /etc/resolv.conf to ../run/
But the above happens during debootstrap so it's probably not what you see. The rest of resolvconf is either trigger by ifupdown, dhclient, network-manager or init but none of these should be running in the install target (or something else is clearly wrong).
I'll try to spend some time this weekend testing this as it's making some of my automated installs (all of these depending on network) fail, not to mention other people's ;)