Ticket #648 (closed defect: fixed)

Opened 14 years ago

Last modified 14 years ago

Installer bails on Lucid due to poor interaction with bind9 and resolvconf

Reported by: jdreed Owned by:
Priority: normal Milestone: Fall 2010
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:  LP:471975


On Lucid installs (possibly only LiveCD-based installs?), resolvconf is installed, but /etc/resolv.conf is not normally a symlink. This causes the bind9 initscript to barf when it tries to call resolvconf.

After setting a static IP with NetworkManager, my /etc/resolv.conf is not a symlink, and has a "# Generated by NetworkManager" line at the top. If I then install -workstation, when it gets to installing bind9, it tries to call resolvconf in the initscript, which barfs with: "Error: /etc/resolv.conf must be a symlink"

Killing the postinst process causes the install to finish normally.

Possible workarounds include:

  • Identifying this situation (having resolvconf installed, but not used) in the Debathena install script and fixing it or giving the user the opportunity to do so.
  • Setting bind9/run-resolvconf to false in debconf

Since this only affects Lucid, there's clearly an upstream bug somewhere, but I don't know where. Insight would be appreciated concerning whether or not this is resolvconf's fault, bind's fault, or networkmanager's fault.

Change History

comment:1 Changed 14 years ago by jdreed

  • Upstream bug set to LP: 471975

Turns out this is a bug when resolvconf and bind9 are installed at the same time (I mistakenly thought resolvconf was installed before I started the debathena-workstation installation).

So perhaps the workaround is easy -- if -workstation is selected, install resolvconf ahead of time.

comment:2 Changed 14 years ago by jdreed

  • Upstream bug changed from LP: 471975 to LP:471975

comment:3 Changed 14 years ago by jdreed

Fixed in r24786.

Evan notes that resolvconf was downgraded to universe, which is why we're seeing this for the first time.

comment:4 Changed 14 years ago by jdreed

  • Status changed from new to committed

This needs testing and then should be pushed out (but not this week)

comment:5 Changed 14 years ago by amb

  • Status changed from committed to closed
  • Resolution set to fixed

This fix had been deployed.

Note: See TracTickets for help on using tickets.