Double confirmed on 20190423-0. For a temporary workaround install insserv-compat and start dhcpd again.