[Bug 516528] Re: [oneiric] Cannot start services on target during autoinstall

[Thomas Ribbrock]

For completeness: ypbind can be used once /sbin/rpcbind is started in
chroot, so there is still a workaround for this regression bug.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/516528

Title:
  [oneiric] Cannot start services on target during autoinstall

Status in “debian-installer” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: debian-installer

  To automatically install identical workstations, we use preseeding in
  conjunction with a netboot. At the end of the installation, we need to
  configure some host-specific values on the machine. To do so, we use
  the following construct:

  d-i preseed/late_command string \
  [...]
  in-target /tmp/set_hostspecific_values;

  "set_hostspecific_values" is of course copied into the right directory
  first.

  Within "set_hostspecific_values", we need to access NIS data related to that machine. In order to do so and use ypcat, we need to start up NIS. In Hardy/8.04, this was possible with
   /etc/init.d/portmap start
   /etc/init.d/nis start

  In Karmic, this fails. With some digging I found that the portmap start fails with some message about portmap being converted to an upstart service and ends with
  start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/ upstart: Connection refused

  Hence, the NIS start fails as well (as portmap is not running) and
  ypcat does not work. I have already found some hints at problems with
  Upstart and chroot environments (which is what the installer uses), so
  I'm not sure whether this is a bug in Upstart or in the installer. In
  any case, I would expect this to work in Karmic as it has in Hardy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/516528/+subscriptions