Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387998
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug was fixed in the package systemd - 245.4-4ubuntu3.2
---
systemd (245.4-4ubuntu3.2) focal; urgency=medium
[ Dan Streetman ]
* Hotadd only offline memory and CPUs (LP: #1876018)
File: debian/extra/rules-ubuntu/40-vm-hotadd.rules
I wasn't able to reproduce this myself, due to the failure being
dependent on timing, but I set up the reproducer from the upstream bug
and rebooted several times with the proposed package, and had no
problems/regressions. Marking this verified.
** Tags removed: verification-needed
This bug was fixed in the package systemd - 245.6-3ubuntu3
---
systemd (245.6-3ubuntu3) groovy; urgency=medium
* Rebuild against libselinux 3.0
systemd (245.6-3ubuntu2) groovy; urgency=medium
* basic/cap-list: Print unknown capabilities in hexadecimal.
This fixes
Hello Michael, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
> Does the Groovy bug task status need fixing?
The g MR is open and linked in this bug; I prefer to leave that up to
@rbalint for the devel release, I'm not sure if he wants to take the
patches or do a merge of newer systemd later.
> But if your trivial patch in comment 7 works, wouldn't that be
@ddstreet
Does the Groovy bug task status need fixing?
I see that in your Focal upload you have a series of seven patches
picked from upstream to fix this properly. But if your trivial patch in
comment 7 works, wouldn't that be better for an SRU? Reference this
paragraph of SRU policy:
"In line
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/386957
--
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/1838329
** Description changed:
+ [impact]
+
+ systems using cryptsetup-based encrypted swap may hang during boot due
+ to udevd missing the notification that swap has been setup on the newly
+ created swap device.
+
+ [test case]
+
+ see original description, and reproduction is intermittent based on
This was (possibly) fixed upstream in a similar way to comment 7:
https://github.com/systemd/systemd/pull/15836
essentially instead of calling mkswap inside flock, it calls systemd-
makefs swap, which itself flocks the block device.
--
You received this bug notification because you are a member
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are
** Tags added: id-5eb44cf735b12c4b9b721452
--
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/1838329
Title:
Cryptswap periodically fails to mount at boot due to missing a
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Focal)
Milestone: None =>
@mmstick76, while I agree with the grumblings upstream that udev should
be better about race conditions like this, if we're working around it
I'd prefer to flock while mkswap instead of retriggering udev...can you
test with that change?
Patch below, and I have test builds for b/f here:
** Tags added: rls-ff-incoming
--
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/1838329
Title:
Cryptswap periodically fails to mount at boot due to missing a udev
Dan, the workaround seems safe and fix a real issue than some users are
hitting, maybe it would make sense to distro patch include it?
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug
** Tags added: ddstreet
--
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/1838329
Title:
Cryptswap periodically fails to mount at boot due to missing a udev
notification
** Changed in: systemd
Status: Unknown => New
--
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/1838329
Title:
Cryptswap periodically fails to mount at boot due to
However, it's unknown when the issue is going to be fixed. So for now
I'm carrying it in Pop!_OS 18.04, 19.04, and 19.10 at the moment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Looks like this still needs to be worked out upstream.
** Bug watch added: github.com/systemd/systemd/issues #10179
https://github.com/systemd/systemd/issues/10179
** Also affects: systemd via
https://github.com/systemd/systemd/issues/10179
Importance: Unknown
Status: Unknown
--
> This patch has already been submitted upstream to systemd
What is the upstream systemd issue number?
--
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/1838329
Title:
The attachment "The workaround for this issue" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned
23 matches
Mail list logo
