[Bug 1005547] Re: on upgrade lucid -> precise /etc/default/isc-dhcp-relay is not migrated

Stéphane Graber stgraber at stgraber.org
Fri Jun 8 15:46:57 UTC 2012


tested here

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  on upgrade lucid -> precise /etc/default/isc-dhcp-relay is not
  migrated

Status in “isc-dhcp” package in Ubuntu:
  Invalid
Status in “isc-dhcp” source package in Precise:
  Fix Committed
Status in “isc-dhcp” source package in Quantal:
  Invalid

Bug description:
  Very similar to bug 1003971.

  /etc/default/dhcp3-relay became /etc/default/isc-dhcp-relay with the 4.x release of isc.
  This file is generated by the maintainer script using debconf keys, so we can't apply the same trick as dhcp3-server.

  The implemented solution is to:
  1) Change dhcp3-server.config in Precise to source /etc/default/dhcp3-relay if present and load the values into debconf
  2) Have the postinst generate /etc/default/isc-dhcp-relay from debconf (showing the previous values to the user)
  3) Have the dhcp3-relay postinst remove any remaining /etc/default/dhcp3-relay

  ----

  [rational]
  Config file isn't migrated, leading to duplicate configuration files and lost settings.

  [test case]
  1) Install dhcp3-relay on Ubuntu 10.04
  2) Use 1.2.3.4 as the server address and eth0 as the interface
  3) (ugly trick) manually update /etc/apt/sources.list to point to precise and include precise-proposed
  4) sudo apt-get update
  5) sudo apt-get install dhcp3-relay (a full dist-upgrade won't work, but selective upgrade of just dhcp3-server will work)
  6) Confirm that debconf is preseeded with the values from the old dhcp3-relay installation and that the resulting generated file in /etc/default/isc-dhcp-relay matches the one from dhcp3-relay. Also ensure that there's no more /etc/default/dhcp3* entries.

  [regression potential]
  If the previous configuration was broken, the new one will be broken too, but that's really what you'd expect from an upgrade...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1005547/+subscriptions




More information about the foundations-bugs mailing list