[Bug 1011470] Re: isc-dhcp-server upstart job incomplete

[Stéphane Graber]

As I mentioned by e-mail to the lxc-users mailing list, the switch to
the upstart job didn't regress the situation, it didn't fix any existing
race condition either.

There's no way of reliably waiting on an ldap server as it's not going
to be guaranteed to be running locally. Same thing for lxc, we can't
make conditional dependencies (if isc-dhcp-server exists, then wait for
it) and can't possibly cope with all the possible use cases our users
might think of.

I don't believe we're currently in a situation where something is broken
on a default install, any other complex configuration might need changes
to the upstart jobs or adding extra jobs to add the dependencies you're
looking for, which is perfectly fine, that's why upstart jobs are config
files after all.

** Changed in: isc-dhcp (Ubuntu)
       Status: New => Opinion

-- 
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/1011470

Title:
  isc-dhcp-server upstart job incomplete

Status in “isc-dhcp” package in Ubuntu:
  Opinion

Bug description:
  As with upgrade from oneiric to precise I have discovered that there
  is new upstart job for isc-dhcp-server which is a minimal "carbon
  copy" of sysv init.d script, and missing major system deps from other
  services.

  Testing it shows that upstart job for isc-dhcp-server indeed is
  incomplete, for example any lxc container starts before isc-dhcp-
  server, and fails to complete startup because can not get assigned
  address (I mean config with lxc-net disabled and br0 configured).

  Being configured to read configuration via ldap service (isc-dhcp-
  server-ldap) it starts before slapd and exits without awaiting to
  start slapd. With a bunch of dependencies between nscd, nslcd, slapd,
  named, autofs-ldap, lxc  - isc-dhcp-server upstart script looks like
  incomplete and incorrect, since does not reflect its dependency on any
  valuable system event or condition, to which real dependants refer.

  Since writing an upstart job script needs careful and complex testing on compatibility with other system services, its better to 
   revert this upstart job to sysv script back, atleast for testing and/or establishing its dependencies.

  I have tried to figure out this upstart dependency on my configuration
  but was unsuccessful, because isc-dhcp-server upstart job needs that
  dependency expressed in upstart jobs from other services, whose init
  scripts are still sysv, and depends on sysv services. So a correct
  rewrite indeed means rewrite all the services starting into upstart,
  not only isc-dhcp-server.

  So, please, revert isc-dhcp-server back to sysv, or provide correct
  startup code.

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