This fix caused a regression in our Dracut-based boot setup.
Since this patch was incorporated (237-3ubuntu10.17), some of several of the 
(PC-type) models we provide to our customers that tend to have "slow I/O", no 
longer boot because Dracut times out waiting for the root file system to come 
online because the systemd-crypt@ service can no longer be started.
We are currently using a build of this source package that doesn't include this 
patch to fix this temporarily.

I have filed a bug eport at Systemd's GitHub too, this contains more 
information:
https://github.com/systemd/systemd/issues/12371.

** Bug watch added: github.com/systemd/systemd/issues #12371
   https://github.com/systemd/systemd/issues/12371

-- 
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/1819728

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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

Reply via email to