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

Bug #1005547 reported by Stéphane Graber on 2012-05-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
isc-dhcp (Ubuntu)
Undecided
Unassigned
Precise
Medium
Stéphane Graber
Quantal
Undecided
Unassigned

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...

Changed in isc-dhcp (Ubuntu Precise):
importance: Undecided → Medium
status: New → Triaged
status: Triaged → In Progress
assignee: nobody → Stéphane Graber (stgraber)
Changed in isc-dhcp (Ubuntu Quantal):
status: New → Invalid
description: updated

Hello Stéphane, or anyone else affected,

Accepted isc-dhcp into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in isc-dhcp (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Stéphane Graber (stgraber) wrote :

tested here

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package isc-dhcp - 4.1.ESV-R4-0ubuntu5.1

---------------
isc-dhcp (4.1.ESV-R4-0ubuntu5.1) precise-proposed; urgency=low

  * Set -pf option for both isc-dhcp-server and isc-dhcp-server6 so they
    create their pid files in a path that's actually writable. (LP: #985417)
  * Also allow read access to the pid file in the apparmor profile,
    otherwise only the initial start succeeds. (LP: #1005062)
  * On upgrade from dhcp3-server, move /etc/default/dhcp3-server to
    /etc/default/isc-dhcp-server. (LP: #1003971)
  * On upgrade from dhcp3-relay, remove /etc/default/dhcp3-relay.
    (LP: #1005547)
  * Try to preseed isc-dhcp-relay with the values from
    /etc/default/dhcp3-relay. (LP: #1005547)
 -- Stephane Graber <email address hidden> Sun, 27 May 2012 20:41:13 -0400

Changed in isc-dhcp (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers