This bug was fixed in the package systemd - 234-2ubuntu10
---------------
systemd (234-2ubuntu10) artful; urgency=medium
* Do not fail debootstrap if /etc/resolv.conf is immutable. (LP: #1713212)
* Revert "Create /etc/resolv.conf on resolved start, if it is an empty file."
As it is ineffective, and correct creation of /etc/resolv.conf has been
fixed.
This reverts commit ccba42504f216f6ffbc54eb2c9af347355f8d86b.
* initramfs-tools: trigger udevadm add actions with subsystems first.
This updates the initramfs-tools init-top udev script to trigger udevadm
actions with type specified. This mimicks the
systemd-udev-trigger.service. Without type specified only devices are
triggered, but triggering subsystems may also be required and should happen
before triggering the devices. This is the case for example on s390x with
zdev
generated udev rules. (LP: #1713536)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 30 Aug 2017 11:22:41
+0100
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713536
Title:
udev: boot script does not trigger subsystem coldplug
Status in Ubuntu on IBM z Systems:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Zesty:
Fix Committed
Status in systemd source package in Artful:
Fix Released
Bug description:
[Impact]
subsystems udev rules are not processed on boot, thus resulting in missing
devices on boot / before rootfs is mounted.
[Solution]
trigger udev subsystems and devices, in the initramfs, in that order.
[Testcase]
Boot s390x system with chzdev configured devices, and cio_ignore=all kernel
command line parameter. The chzdev configured devices should still be
discovered on boot.
[Original Bug report]
The udev initramfs-tools boot script does not trigger subsystem "add"
uevents. As a result, udev rules that listen to subsystem "add" events
are never activated. This problem exists on at least Ubuntu 16.04 and
17.10.
On s390, this results in a boot failure if the kernel is configured to
start with an active device black list (kernel parameter
cio_ignore=all,!condev). An example for an affected udev rule looks
like this:
ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
/proc/cio_ignore'"
A proposed fix would be:
Modify /usr/share/initramfs-tools/scripts/init-top/udev:
Replace line
udevadm trigger --action=add
with
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add
This would also be consistent with the steps that the systemd udev
coldplug unit file performs (see /lib/systemd/system/systemd-udev-
trigger.service).
[Regression Potential]
More udev rules will be now triggered, earlier, during initramfs stage of
boot rather than post-pivot-root. However, this is inline with current rootfs
behaviour and thus should not regress behaviour - simply some rules will get
triggered earlier.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
