group.of.nepali.translators team mailing list archive

[Michael Vogt <michael.vogt@xxxxxxxxxxxxx>]

Unfortunately we need to pull the xenial update. We see failure like
this:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/i386/p/python-
systemd/20190314_173156_e1077@/log.gz

on various autopkgtest runs. E.g. for
http://autopkgtest.ubuntu.com/packages/p/python-systemd

It is also very inconsistent, i.e. not all arches are affected, for the
python-systemd just i386,ppc64el,s390x. But its also visible in the
docker.io xenial amd64 test so its not arch specific.

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  Triaged
Status in systemd source package in Bionic:
  Fix Committed

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".

  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]
  Low, this change is already in the systemd upstream and in use cosmic and later.

  The upstream fix is https://github.com/systemd/systemd/pull/8803
  Full spread run with the fixed systemd in the "core" snap and a regression test: https://github.com/snapcore/snapd/pull/6595

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