DNS not setup correctly (Lucid beta)

Reported by Peter on 2010-06-20
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
TurnKey Linux
Fix Released
High
Alon Swartz

Bug Description

In the lucid beta during the boot sequence it does not correctly setup the DNS server using DHCP.

This can be fixed by doing a udhcpc renew however this needs to be done after each reboot.

Alon Swartz (alonswartz) on 2010-06-20
Changed in turnkeylinux:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Alon Swartz (alonswartz)
Jeremy Davis (jedmeister) wrote :

Obviously setting it manually in config console is another workaround (which survives reboot).

Jackey Yang (jackey-yang-gmail) wrote :

udhcpc renew is not final solution for this. U can put into /etc/rc.local. But LiveCD won't be able to boot if you have it in /etc/rc.local.
This needs a real fix.

Neil Wilson (neil-aldur) wrote :

The problem appears to be a race condition between the upstart networking system and the 'resolvconf' package. That package isn't in the standard Lucid server distribution, and the solution appears to be to remove it from Turnkey as well.

Unless its used by something else of course...

Liraz (liraz-siri) wrote :

We're trying to get to the bottom of this now. FYI, resolvconf is used by the confconsole to support nameserver configuration for multiple NICs. Upstart opened a whole can of whoop ass with all of this additional complexity. Argh!

Liraz (liraz-siri) wrote :

We traced this back to yet another Upstart-related regression in Ubuntu Lucid. Now that Upstart is out of compatibility mode and has started to replace sysvinit in earnest, the old init scripts and the new are clashing and it's ugly.

IMHO, more could have been done to increase Upstart's compatibility with the old init scripts. The old init scripts already documented their dependencies for insserv, and with a bit of clever coding Upstart could have done something useful with that information, at least while we're still transitioning from the old system to the new. Flagging all reports of regressions as invalid isn't as helpful. Sigh. Ubuntu is infuriating sometimes.

For the record resolvconf really shouldn't be in universe. It's an infrastructural package closely related to the core networking scripts. That's the way it is in Debian, that's the way it should be in Ubuntu.

Anyhow, there's a fix for this that didn't make it into the LTS:

https://bugs.launchpad.net/ubuntu/lucid/+source/upstart/+bug/448095

Don't worry though, we'll incorporate this into the next release.

Alon Swartz (alonswartz) wrote :

We've forked the originally Ubuntu package, and applied the fix the posted in the link Liraz mentioned.
I've tested the new package and it fixes this bug.

It will be included in the upcoming release. In the meantime I'll upload the new package to the turnkey repos so it can be installed on the lucid-beta-core,

Changed in turnkeylinux:
status: Confirmed → Fix Committed
Jeremy Davis (jedmeister) wrote :

Fix released and included in TKL v11.0 on

Changed in turnkeylinux:
status: Fix Committed → Fix Released
summary: - DNS not setup correctly (lucid beta)
+ DNS not setup correctly (TKL v11.x - Lucid based)
summary: - DNS not setup correctly (TKL v11.x - Lucid based)
+ DNS not setup correctly (Lucid beta)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers