[systemd-devel] issues with systemd-cryptsetup at .service after in 251-rc3

[Dusty Mabe]

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 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:
>>
>>>>> [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
>>
>> No idea. There were a few changes to udev and sd-device, and it's
>> possible that they caused some regression. But I don't see anything
>> obvious.
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=87360713 has a
> scratch builds with one patch reverted.  Could you test if it fixes
> the issue?

Just tested a build of FCOS with that scratch build included. It passes our
tests now so it looks like it was that patch that was the problem.


Dusty