Re: [PATCH 0/3] Detect systemd services ordering cycle

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 21.08.24 06:49, Uladzimir Bely wrote:
> On Fri, 2024-08-16 at 17:38 +0300, Uladzimir Bely wrote:
>> Merging v3 of "expand-on-first-boot: Ensure that /tmp is writable"
>> led to systemd services ordering cycle. Systemd randomly drops one
>> of sycled services and sometimes it's "expand-on-first-boot" one.
>>
>> This patchset reverts version 3 of the patch and returns to
>> previous version.
>>
>> Additionally, we extend CI so that qemu run tests could always detect
>> any systemd services ordering cycles.
>>
>> Clara Kowalsky (1):
>>   expand-on-first-boot: Add /tmp to ConditionPathIsReadWrite
>>
>> Uladzimir Bely (2):
>>   Revert "expand-on-first-boot: Ensure that /tmp is writable"
>>   testsuite: Detect systemd services ordering cycle
>>
>>  .../expand-on-first-boot/files/expand-on-first-boot.service  | 3 +--
>>  testsuite/cibuilder.py                                       | 5
>> +++++
>>  2 files changed, 6 insertions(+), 2 deletions(-)
>>
>> -- 
>> 2.44.2
>>
> 
> Applied to next.
> 

Still broken:

root@isar:~# journalctl -u expand-on-first-boot
-- Boot 336ca3ef86c74a06ab8e11e40a321c84 --
Jun 16 09:44:32 isar systemd[1]: expand-on-first-boot.service - Expand last partition was skipped because of an unmet condition check (ConditionPathIsReadWrite=/etc /tmp).
root@isar:~# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-6.1.0-23-amd64 root=PARTLABEL=platform rw rootwait console=ttyS0,115200 console=tty0

Patch will follow.

Why didn't you test this?

Jan

-- 
Siemens AG, Technology
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/cb630784-3b27-483a-8bd2-5beed2462d2a%40siemens.com.