DNS doesn't work as expected -- ldap-server, kerberos-server not found.

Bug #971046 reported by Thomas Schweikle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Problem: upgrade overwrites /etc/ldap/ldap.conf. Doesn't take given config to configure dconfig, creating useful dconfig for ldap.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-2
ProcVersionSignature: Ubuntu 3.2.0-21.34-virtual 3.2.13
Uname: Linux 3.2.0-21-virtual i686
ApportVersion: 2.0-0ubuntu2
Architecture: i386
Date: Sun Apr 1 21:27:06 2012
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 TERM=screen-bce
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-2
 apparmor 2.7.102-0ubuntu2
SourcePackage: bind9
UpgradeStatus: Upgraded to precise on 2012-04-01 (0 days ago)
modified.conffile..etc.apparmor.d.usr.sbin.named: [modified]
modified.conffile..etc.bind.bind.keys: [deleted]
modified.conffile..etc.bind.db.0: [deleted]
modified.conffile..etc.bind.db.127: [deleted]
modified.conffile..etc.bind.db.255: [deleted]
modified.conffile..etc.bind.db.empty: [deleted]
modified.conffile..etc.bind.db.local: [deleted]
modified.conffile..etc.bind.db.root: [deleted]
modified.conffile..etc.bind.named.conf: [deleted]
modified.conffile..etc.bind.named.conf.default.zones: [deleted]
modified.conffile..etc.bind.named.conf.local: [deleted]
modified.conffile..etc.bind.zones.rfc1918: [deleted]
modified.conffile..etc.init.d.bind9: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.named: 2011-01-18T16:00:35
mtime.conffile..etc.init.d.bind9: 2011-04-18T15:18:30

Revision history for this message
Thomas Schweikle (tps) wrote :
Revision history for this message
Thomas Schweikle (tps) wrote :

Config partly overwritten by update.

Revision history for this message
Thomas Schweikle (tps) wrote :

Rendering remaining configuration unusable.

Revision history for this message
James Page (james-page) wrote :

Hi Thomas

The bug title and description appear to be un-related.

Assuming this is related to the other bugs you have reported please could explain in a bit more detail what your overall configuration looks like and what issues you have had when upgrading.

Thanks

Changed in bind9 (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Thomas Schweikle (tps) wrote :

Install isc-dhsp-server on a host, configure it, then deactivate it, aka make it not to start while the system is booting.
Upgrade this server from oneiric to precise.
Watch the upgrade break because isc-dhcp-server exausting error "1" (what is quite OK, since it is installed, but meant to not start --- why this case is handled as error --- ??).

There are two choices to get the upgrade done:
1. remove isc-dhcp-server, resume the upgrade, install isc-dhcp-server again
2. allow isc-dhcp-server to start, risking a mess because two dhcp-servers working on the very same subnet

The upgrade will resume seamlessly in both cases.

This is not related to the other bugs reported. It is just an other one, and at an other, totaly distinct place, unrelated to anything reported before. It is just something that shouldn't happen. It may be reported isc-dhcp-server could not start, but this fact should not lead to stopping a running upgrade of the remaining packages installed!

Revision history for this message
Thomas Schweikle (tps) wrote :

Just ignore comment #5. It is for bug 979720. Not for this one!

Revision history for this message
Thomas Schweikle (tps) wrote :

Now the rigth one.

This bug is not related to bind9, but to OpenLDAP. OpenLDAP has two configuration files for authenticating against a ldap-server:
/etc/ldap/ldap.conf -- used by nsswitch
/etc/ldap.conf -- used by other tools

Both of these files are overwritten by "do-release-upgrade -d", breaking the connection to your ldap-server.

Revision history for this message
James Page (james-page) wrote :

Hi Thomas

Thanks for the extra info - sound like this is also the underlying cause of bug 971028 as well so I'm going to dupe them for the time being (we can always split them later if it turns out not to be the case).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.