[Bug 989585] Re: resolvconf failed to install/upgrade because /etc/resolv.conf immutable

Launchpad Bug Tracker 989585 at bugs.launchpad.net
Tue May 22 21:47:11 UTC 2012


This bug was fixed in the package resolvconf - 1.63ubuntu14

---------------
resolvconf (1.63ubuntu14) precise-proposed; urgency=low

  * Call db_go after the db_input command so that the debconf error
    message is actually shown to the user.

resolvconf (1.63ubuntu13) precise-proposed; urgency=low

  [ Stéphane Graber ]
  * In is_immutable_file, if lsattr doesn't return anything on stdout,
    return 1 and hide stderr. This fixes lsattr failing on non-ext
    filesystems. (LP: #994539)

  [ Steve Langasek ]
  * Fix syntax of db_input command, which is part of why we're seeing
    failures in bug #994539.

resolvconf (1.63ubuntu12) precise-proposed; urgency=low

  * Instead of throwing an error that aborts the upgrade when
    /etc/resolv.conf is immutable, pop a debconf error message to let the
    user know what's happening, then clear the immutable flag and continue
    with the installation.  LP: #989585.
 -- Stephane Graber <stgraber at ubuntu.com>   Mon, 14 May 2012 12:31:58 -0400

** Changed in: resolvconf (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/989585

Title:
  resolvconf failed to install/upgrade because /etc/resolv.conf
  immutable

Status in “resolvconf” package in Ubuntu:
  Fix Released
Status in “resolvconf” source package in Precise:
  Fix Released
Status in “resolvconf” source package in Quantal:
  Fix Released

Bug description:
  [Impact] because Network Manager historically would overwrite users'
  local DNS resolver settings on the desktop, a fair number of users
  have marked this file immutable on the filesystem.  This causes an
  upgrade failure when going to 12.04, which makes resolvconf a non-
  optional part of the infrastructure for all users and requires
  /etc/resolv.conf to be replaced by a symlink.

  [Development Fix]
  resolvconf is arch: all and should be pocket-copied to quantal after SRU accept.

  [Test Case]
  1.  Install Ubuntu 11.10
  2.  run: sudo chattr +i /etc/resolv.conf
  3.  do a release upgrade to 12.04
  4.  verify that the upgrade fails with an error from the resolvconf package.
  5.  enable -proposed
  6.  attempt the release upgrade again
  7.  verify that the upgrade completes successfully, and that /etc/resolv.conf has been made a symlink.

  [Regression Potential]
  Since this overrides a filesystem bit that's been explicitly set by the admin, some users may be unhappy with this change.  But this is not a supported configuration, so this should not block the SRU.

  Failed to install during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: resolvconf 1.63ubuntu11
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  AptOrdering:
   unity-scope-musicstores: Install
   resolvconf: Configure
   ubuntu-minimal: Configure
   unity-scope-musicstores: Configure
  Architecture: amd64
  Date: Fri Apr 27 11:23:12 2012
  DuplicateSignature:
   Setting up resolvconf (1.63ubuntu11) ...
   resolvconf.postinst: Error: Cannot replace the current /etc/resolv.conf with a symbolic link because it is immutable. To correct this problem, gain root privileges in a terminal and run 'chattr -i /etc/resolv.conf' and then 'dpkg --configure resolvconf'. Aborting.
   dpkg: error processing resolvconf (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  PackageArchitecture: all
  SourcePackage: resolvconf
  Title: package resolvconf 1.63ubuntu11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago)

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




More information about the foundations-bugs mailing list