Activity log for bug #1713536

Date Who What changed Old value New value Message
2017-08-28 16:59:20 bugproxy bug added bug
2017-08-28 16:59:22 bugproxy tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604
2017-08-28 16:59:23 bugproxy ubuntu: assignee Skipper Bug Screeners (skipper-screen-team)
2017-08-28 16:59:26 bugproxy affects ubuntu initramfs-tools-ubuntu-touch (Ubuntu)
2017-08-28 20:43:34 Steve Langasek affects initramfs-tools-ubuntu-touch (Ubuntu) systemd (Ubuntu)
2017-08-29 07:10:53 Andrew Cloke bug task added ubuntu-power-systems
2017-08-29 07:10:59 Andrew Cloke ubuntu-power-systems: importance Undecided Medium
2017-08-29 07:11:12 Andrew Cloke ubuntu-power-systems: assignee Canonical Foundations Team (canonical-foundations)
2017-08-29 11:17:34 Dimitri John Ledkov affects ubuntu-power-systems ubuntu-z-systems
2017-08-29 11:19:14 Dimitri John Ledkov systemd (Ubuntu): status New Confirmed
2017-08-29 11:19:32 Dimitri John Ledkov nominated for series Ubuntu Xenial
2017-08-29 11:19:32 Dimitri John Ledkov bug task added systemd (Ubuntu Xenial)
2017-08-29 11:19:32 Dimitri John Ledkov nominated for series Ubuntu Artful
2017-08-29 11:19:32 Dimitri John Ledkov bug task added systemd (Ubuntu Artful)
2017-08-29 11:19:32 Dimitri John Ledkov nominated for series Ubuntu Zesty
2017-08-29 11:19:32 Dimitri John Ledkov bug task added systemd (Ubuntu Zesty)
2017-08-29 14:26:24 Christian Ehrhardt  bug added subscriber ChristianEhrhardt
2017-08-30 10:11:33 Dimitri John Ledkov systemd (Ubuntu Artful): status Confirmed Fix Committed
2017-08-31 10:13:52 Dimitri John Ledkov systemd (Ubuntu Zesty): status New In Progress
2017-09-04 10:46:43 Dimitri John Ledkov description 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). [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).
2017-09-04 10:49:41 Dimitri John Ledkov 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). [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.
2017-09-05 10:56:48 Dimitri John Ledkov systemd (Ubuntu Xenial): status New In Progress
2017-09-07 18:05:27 Brian Murray systemd (Ubuntu Zesty): status In Progress Fix Committed
2017-09-07 18:05:30 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-09-07 18:05:32 Brian Murray bug added subscriber SRU Verification
2017-09-07 18:05:36 Brian Murray tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-needed verification-needed-zesty
2017-09-11 05:20:43 Frank Heimes ubuntu-z-systems: status New In Progress
2017-09-11 12:19:40 bugproxy tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-needed verification-needed-zesty architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done verification-done-zesty
2017-09-14 16:52:47 Launchpad Janitor systemd (Ubuntu Artful): status Fix Committed Fix Released
2017-09-19 15:24:06 Brian Murray systemd (Ubuntu Xenial): status In Progress Fix Committed
2017-09-19 15:24:12 Brian Murray tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done verification-done-zesty architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done-zesty verification-needed verification-needed-xenial
2017-09-19 15:53:01 Frank Heimes ubuntu-z-systems: status In Progress Fix Committed
2017-10-04 13:53:11 Dimitri John Ledkov tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done-zesty verification-needed verification-needed-xenial architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done verification-done-xenial verification-done-zesty
2017-10-05 17:32:18 Brian Murray tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done verification-done-xenial verification-done-zesty architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done-xenial verification-needed verification-needed-zesty
2017-10-10 08:01:54 Dimitri John Ledkov tags architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done-xenial verification-needed verification-needed-zesty architecture-s39064 bugnameltc-158070 severity-medium targetmilestone-inin1604 verification-done verification-done-xenial verification-done-zesty
2017-10-11 19:24:47 Nobuto Murata bug added subscriber Nobuto Murata
2017-10-23 12:13:02 Launchpad Janitor systemd (Ubuntu Xenial): status Fix Committed Fix Released
2017-10-23 12:13:32 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2017-10-23 14:09:28 Frank Heimes ubuntu-z-systems: status Fix Committed Fix Released
2017-10-26 14:28:26 Launchpad Janitor systemd (Ubuntu Zesty): status Fix Committed Fix Released