Bug 835812 - udev update may kill udevmountd
Summary: udev update may kill udevmountd
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: 13.1 Milestone 4
Hardware: x86-64 openSUSE 12.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard: SILVER
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 07:21 UTC by Marius Tomaschewski
Modified: 2015-04-09 06:33 UTC (History)
8 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
hare: needinfo? (mt)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Tomaschewski 2013-08-21 07:21:18 UTC 
+++ This bug was initially created as a clone of Bug #821879 +++

Reproducible: Always

Steps to Reproduce:
have a 12.3 x86_64 VM with eth0 configured for dhcp4
ssh to the VM and do
zypper in udev-195-13.25.1

Actual Results:
Installing: udev-195-13.25.1 ...............<50%>====================[\]
in the middle of udev installation, network goes down, no dhcpcd running

* See comment #70:

Here is the exact explanation from upstream NEWS:

        * udev: when udevd is started by systemd, processes which are left
          behind by forking them off of udev rules, are unconditionally cleaned
          up and killed now after the event handling has finished. Services or
          daemons must be started as systemd services. Services can be
          pulled-in by udev to get started, but they can no longer be directly
          forked by udev rules.


This seems to mean, the udev rules may need to use:

   SYSTEMD_WANTS="udevmountd@XXXX.service"

instead, with a service template like this:

[Unit]
Description=udevmountd for %i
BindsTo=....%i.device

[Service]
ExecStart=/usr/lib/udev/udevmountd %i
Comment 1 Hannes Reinecke 2013-11-19 09:10:40 UTC 
As per discussion with Kay Sievers the udevmountd functionality is now implemented in systemd, so udevmountd isn't required anymore when using systemd. To provide equivalent functionality you'd need to specify 'nofail' in /etc/fstab; that option is parsed by systemd and everything will work as expected.

Not sure if there's something which needs to be done here, except for specifying 'nofail' ...
Comment 2 Marcus Rückert 2013-11-19 11:21:37 UTC 
maybe document it prominently in the wiki and release notes?
Comment 3 Hannes Reinecke 2015-04-09 06:33:27 UTC 
Leave this issue to rest. Equivalent functionality is being provided with systemd and udevmountd will not be used going forward.