Re: issues with systemd-cryptsetup@.service after in 251-rc3

[Daan De Meyer <daan.j.demeyer@xxxxxxxxx>]

I'd also recommend opening an issue on the upstream issue tracker
(https://github.com/systemd/systemd/issues). It'd be great if you
could include a full journal (just zip up /var/log/journal) and the
contents of systemd-cryptsetup@myluksdev.service if possible to help
with debugging.

Cheers,

Daan

On Thu, 19 May 2022 at 08:05, Paul Menzel
<pmenzel+systemd-devel@xxxxxxxxxxxxx> wrote:
>
> Dear Dusty,
>
>
> Am 19.05.22 um 05:32 schrieb Dusty Mabe:
> > I'm requesting help to try to find a problematic commit between
> > v251-rc2..v251-rc3.
> >
> > We have a test in Fedora CoreOS [1] that tests luks and this test
> > started failing in our rawhide stream with the introduction of
> > 251-rc3. Reverting back to 251-rc2 makes the failing test go away. I
> > briefly looked at the commits from v251-rc2..v251-rc3 but nothing
> > jumped out at me.
> >
> > Any commits in there that we think might be risky or ones we should
> > look at closer?
>
> Please bisect. It’s the most efficient way, and you can do it yourself,
> especially as you have a test to reproduce the issue.
>
> > Here's the original bug [2] I opened against Fedora CoreOS:
>
>
> Kind regards,
>
> Paul
>
>
> > [1] https://github.com/coreos/fedora-coreos-config/tree/testing-devel/tests/kola/root-reprovision/luks
> > [2] https://github.com/coreos/fedora-coreos-tracker/issues/1200