On 5/22/22 08:35, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, May 20, 2022 at 03:51:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
>> On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
Am 19.05.22 um 05:32 schrieb Dusty Mabe:
> I'm requesting help to try to find a
On Fri, May 20, 2022 at 03:51:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
> > > 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.
> > > >
>
On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
> > 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
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,
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
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
