[Bug 811823] [NEW] idmapd upstart job ends in an inconsistent state if /usr is a separate partition

[Steve Langasek]

Public bug reported:

Because the idmapd upstart job uses a script line instead of directly
exec'ing the server, in the case where /usr is a separate partition and
not yet mounted at the time the job is started (e.g., because an NFS
mount is attempted in parallel to an fsck of /usr), the job will fail to
start and get wedged in a 'start/running' state with no associated PID
(upstart bug #545673).  If we exec the daemon directly, upstart will
detect the exec() failure and respawn as needed.

This partially addresses the problems described in bug #643289, and is
worth SRUing in its own right even though it doesn't provide a complete
solution for all users.

** Affects: nfs-utils (Ubuntu)
     Importance: Medium
     Assignee: Steve Langasek (vorlon)
         Status: Triaged

** Affects: nfs-utils (Ubuntu Lucid)
     Importance: Medium
     Assignee: Steve Langasek (vorlon)
         Status: Triaged

** Affects: nfs-utils (Ubuntu Maverick)
     Importance: Medium
     Assignee: Steve Langasek (vorlon)
         Status: Triaged

** Affects: nfs-utils (Ubuntu Natty)
     Importance: Medium
     Assignee: Steve Langasek (vorlon)
         Status: Triaged

** Changed in: nfs-utils (Ubuntu)
       Status: New => Triaged

** Changed in: nfs-utils (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nfs-utils (Ubuntu)
     Assignee: (unassigned) => Steve Langasek (vorlon)

** Also affects: nfs-utils (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Also affects: nfs-utils (Ubuntu Maverick)
   Importance: Undecided
       Status: New

** Also affects: nfs-utils (Ubuntu Natty)
   Importance: Undecided
       Status: New

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

Title:
  idmapd upstart job ends in an inconsistent state if /usr is a separate
  partition

Status in “nfs-utils” package in Ubuntu:
  Triaged
Status in “nfs-utils” source package in Lucid:
  Triaged
Status in “nfs-utils” source package in Maverick:
  Triaged
Status in “nfs-utils” source package in Natty:
  Triaged

Bug description:
  Because the idmapd upstart job uses a script line instead of directly
  exec'ing the server, in the case where /usr is a separate partition
  and not yet mounted at the time the job is started (e.g., because an
  NFS mount is attempted in parallel to an fsck of /usr), the job will
  fail to start and get wedged in a 'start/running' state with no
  associated PID (upstart bug #545673).  If we exec the daemon directly,
  upstart will detect the exec() failure and respawn as needed.

  This partially addresses the problems described in bug #643289, and is
  worth SRUing in its own right even though it doesn't provide a
  complete solution for all users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/811823/+subscriptions