touch-packages team mailing list archive

[Cs-gon <1392297@xxxxxxxxxxxxxxxxxx>]

I have debugged this problem further:

The problem seems to be that the postinst script executes "invoke-rc.d
resolvconf start", which indeed seems to execute the init script
/etc/init.d/resolvconf during the installation of the package. There is
no /usr/sbin/policy-rc.d in the target system, so the execution of the
init script is not suppressed.

When running the postinst script on it's own, it moves the original
/etc/resolv.conf file to /run/resolvconf/resolv.conf and links
/etc/resolv.conf to it. So far so good. But when "/etc/init.d/resolvconf
start" gets called as a result of "invoke-rc.d resolvconf start", the
contents of /run/resolvconf get removed (resolvconf ---wipe-runtime-
directories), and a new and empty resolv.conf gets created (resolvconf
--enable-updates).

After that the subsequent installation steps, which try to access the
network, fail.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1392297

Title:
  resolvconf 1.69ubuntu1.1 breaks network install

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  We are experiencing problems with Ubuntu 14.04 network installations,
  when using the 1.69ubuntu1.1 version of resolvconf. With this version
  the file /etc/resolv.conf gets reset to an empty file (does only
  include just the standard resolvconf comments) during the installation
  of the resolvconf package. After that the name resolution doesn't work
  anymore and the subsequent installation steps fail.

  If we use the 1.69ubuntu1 version, everything works fine.

  If I make a diff of both package contents, the most significant change
  seems to be the inclusion of a new Sys-V init script, which (besides
  other things) removes the contents of the resolvconf runtime
  directories when called with the option "start", and the postinst
  script calls "invoke-rc.d resolvconf start" at the end (included by
  dh_installinit), which I think should do nothing during the
  installation because of policy-rc.d (right?), but I wonder if it
  actually get's called and removes the resolv.conf file that got
  migrated to the runtime directories earlier in the postinst script. At
  least that would explain our problems, because I don't really see
  anything else, that could cause this problem.

  I see that the inclusion of the new init script is coming from debian,
  and they call the dh_installinit with the option "--no-start" in
  debian/rules, while the Ubuntu package calls the dh_installinit only
  with the option "-r". And debian inserts the debhelper code a lot
  earlier in the postinst script.

  Could this be what's causing the problem? As soon I have more time, I
  will try to debug this further and provide more information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions