Valentin Vidic <[email protected]> writes:
> On Sun, Feb 23, 2025 at 01:13:14PM +0100, Chris Hofstaedtler wrote:
>
>> It appears the test is flaky, a retry passed:
>>
>> https://ci.debian.net/packages/d/dlm/unstable/amd64/58083508/
>>
>> Please investigate and/or mark the test as flaky.
>
> I cannot reproduce the problem locally unfortunately. The only
> strage thing I see in the logs is failing to start the service
> after installation:
>
> 191s Setting up dlm-controld (4.3.0-1+b1) ...
> 192s Created symlink
> '/etc/systemd/system/multi-user.target.wants/dlm.service' →
> '/usr/lib/systemd/system/dlm.service'.
> 202s Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
>
> Since the test expects the service to be running, that would
> explain the test failure. But it is not clear why the service
> failed to start in the first place.
Is the VM running the test managed by systemd?
What is its kernel version? Current DLM Git tip says:
This patch should work with the updated kernel dlm module, because
the code changes need to be aligned with the DLM_MAX_ADDR_COUNT value.
But that patch is not in Debian yet.
--
Regards,
Feri.
