[Bug 1466081] Re: [udev] no uevent when block devices change

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 220-7ubuntu1

---------------
systemd (220-7ubuntu1) wily; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-top: Drop scsi_wait_scan and udevadm settle, we do that
      in a more sensible way with wait-for-root.
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
      script.
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup at .service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521) Also run ifup in the background during boot,
      to avoid blocking network.target. (LP: #1425376)
    - ifup at .service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - systemctl: Don't forward telinit u to upstart. This works around
      upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
      that changes to point to systemd during the upgrade. This avoids running
      systemd during a dist-upgrade. (LP: #1430479)
    - Drop hwdb-update dependency from udev-trigger.service, which got
      introduced in v219-stable. This causes udev and plymouth to start too
      late and isn't really needed in Ubuntu yet as we don't support stateless
      systems yet and handle hwdb.bin updates through dpkg triggers. This can
      be dropped again with initramfs-tools 0.117.
    - Lower Breaks: to plymouth version which has the udev inotify fix in
      Ubuntu.
    - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs.
    - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.

systemd (220-7) unstable; urgency=medium

  [ Michael Biebl ]
  * Enable seccomp support on arm64 as well.
  * Replace the remainder of Fix-paths-in-man-pages.patch with an upstream
    provided patch.

  [ Martin Pitt ]
  * Switch to net.ifnames persistant network interfaces (on new
    installations/for new hardware), and deprecate the old
    75-persistent-net-generator.rules. See the ML discussion for details:
        https://lists.debian.org/debian-devel/2015/05/msg00170.html
        https://lists.debian.org/debian-devel/2015/06/msg00018.html
    - Drop Make-net.ifnames-opt-in-instead-of-opt-out.patch, to use
      net.ifnames by default.
    - Revert-udev-network-device-renaming-immediately-give.patch: Adjust
      patch comment.
    - Drop 75-persistent-net-generator.rules, write_net_rules helper and
      rule_generator.functions.
    - Adjust udev's README.Debian accordingly, and describe the migration.
      This needs to happen manually as there is no robust way of doing this
      automatically.
    - Add udev NEWS file for announcing this change and pointing to udev's
      README.
    - udev.postinst: Drop write_interfaces_rules().
    - udev.postinst: Disable net.ifnames on systems which did not support
      75-persistent-net-generator.rules (most importantly, virtualized guests)
      to avoid changing network interface names on upgrade.
    - LP: #1454254
  * fsckd-daemon-for-inter-fsckd-communication.patch: Add fsckd.c to
    POTFILES.in.
  * ifupdown-hotplug autopkgtest: Fix config name in interfaces.d/, it must
    not have a suffix in Debian. Also clean up the file after the test.
  * net.agent: When running under systemd, run everything in the foreground.
    This avoids killing the forked child in the middle of its operation under
    systemd when the parent exits.
  * Check during build that systemd and systemd-journald don't link against
    anything in /usr, to prevent bugs like #771652 and #788913 in the future.
  * Drop Skip-99-systemd.rules-when-not-running-systemd-as-in.patch. The rules
    mostly just attach tags systemd specific properties which are harmless
    under other init systems, and systemd-sysctl also works there.
  * 80-networking.rules: Only call agents for add|remove, as they don't handle
    other events.
  * Restore udev watches on block device changes. (Closes: #789060,
    LP: #1466081)

 -- Martin Pitt <martin.pitt at ubuntu.com>  Wed, 17 Jun 2015 23:24:31
+0200

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  [udev] no uevent when block devices change

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  New

Bug description:
  Since July 7, udisks2 fails its tests:
  https://jenkins.qa.ubuntu.com/job/wily-adt-udisks2/

  After a file system operation like mkfs or e2label udisks2 does not
  update its properties any more. This can be replicated easily locally
  with e. g.

    sudo modprobe scsi_debug
    sudo mkfs.ext2 -L old /dev/sda
    udisksctl info -b /dev/sdb
    # -> no IdType, IdLabel, etc.

  It starts being correct after manually triggering an uevent with "sudo
  udevadm trigger -v --sysname-match=sdb".

  Upstream bug: https://github.com/systemd/systemd/issues/255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466081/+subscriptions