Ok, I just tried with this version, and the issue I am seeing sadly does
persist. So, this does not resolve it. Please ignore the last comment.
Sorry,
Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks for porting this to Xenial. Should the Xenial Ubuntu Base
release be updated? The Ubuntu Base 16.04.3 does come with the
problematic systemd, and on some systems, like the armhf, booting to a
bare rootfs is impossible (always get the issue, which manifest itself
as 'A start job is running
This bug was fixed in the package systemd - 229-4ubuntu21.1
---
systemd (229-4ubuntu21.1) xenial-security; urgency=medium
* SECURITY UPDATE: remote DoS in resolved (LP: #1725351)
- debian/patches/CVE-2017-15908.patch: fix loop on packets with pseudo
dns types in src/resolv
This bug was fixed in the package systemd - 232-21ubuntu7
---
systemd (232-21ubuntu7) zesty; urgency=medium
* networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
* networkd: add support for ActiveSlave and PrimarySlave netdev options.
(LP: #1709135)
* Cherryp
Reproduced hang with systemd 232-21ubuntu5.
Upgrading to 232-21ubuntu7 resolves the race.
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello Pegerto, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Description changed:
+ [Impact]
+ In systemd prior to 234 a race exists between .mount and .automount units
such that automount requests from kernel may not be serviced by systemd
resulting in kernel holding the mountpoint and any processes that try to use
said mount will hang. A race like t
Artful has this change already.
Zesty and Xenial need this cherry-pick.
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: Confirmed
** Changed in: systemd (Ubuntu Artful)
Sta
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of U
Hi Dimitri,
We are affected by that,too.
We have no advantage support.
We have multiple server parks with 3000+ Ubuntu machines.
We sees this this bug triggering especially, if some
program/container/pod is using auto mount directly after startup.
We worked around this issue by manually patchin
There is no time commitment for this request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709649
Title:
229 backport for race between explicit mount and handling automount
To manage notificatio
When you say "we" - who do you mean? Do you per chance have Ubuntu
Advantage and/or any other support contracts? If that is the case,
please note, you must use UA portal to escalate issues.
Please note the bug report is incomplete w.r.t. infomration of the affected
systems. Please use
$ ubuntu-bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709649
Title:
22
13 matches
Mail list logo
