Re: [PATCH v3 0/2] Enable systemd units based on systemd presets

[Zhihang Wei <wzh@ilbers.de>]

Hi,

when testing this patch on CI, the following test failed:
- citest.py:DevTest.test_dev

Error log from avocado:
2025-10-22 17:42:41,056 cibuilder        L0322 ERROR| ERROR: 
mc:qemuarm-bookworm:isar-image-base-sdk-1.0-r0 do_rootfs_postprocess: 
ExecutionError('/work/build/tmp/work/debian-bookworm-armhf/isar-image-base-sdk-qemuarm/1.0-r0/temp/run.image_postprocess_populate_systemd_preset.287029', 
127, None, None)
2025-10-22 17:42:41,059 cibuilder        L0322 ERROR| ERROR: Logfile of 
failure stored in: 
/work/build/tmp/work/debian-bookworm-armhf/isar-image-base-sdk-qemuarm/1.0-r0/temp/log.do_rootfs_postprocess.287029
......
2025-10-22 17:42:41,983 cibuilder        L0322 ERROR| ERROR: Task 
(mc:qemuarm-bookworm:virtual:sdk:/work/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs_postprocess) 
failed with exit code '1'
......

Error log from log.do_rootfs_postprocess.287029:
......
DEBUG: Executing shell function rootfs_cleanup_isar_apt
DEBUG: Shell function rootfs_cleanup_isar_apt finished
DEBUG: Executing shell function image_postprocess_populate_systemd_preset
chroot: failed to run command ‘systemctl’: No such file or directory
WARNING: exit code 127 from a shell command.
DEBUG: Executing shell function rootfs_do_umounts
DEBUG: Shell function rootfs_do_umounts finished
DEBUG: Python function do_rootfs_postprocess finished

You can redo the test on your machine using avocado:
1. Have a clean clone of isar, checkout to branch next and apply your 
patches:
$ git clone -b next https://github.com/ilbers/isar.git
$ cd isar
$ git am /path-to/0001-my-contribution-to-isar.patch
2.Run kas shell, setup CI prerequisites (avocado, qemu) and cleanup:
$ ./kas/kas-container shell kas/isar.yaml --command \
     "rm -rf /work/build/conf && /work/scripts/ci_setup.sh"
3.Run the failed test:
$ cd /work/testsuite
$ avocado run citest.py:DevTest.test_dev --max-parallel-tasks=1

On my machine (CPU: AMD 7840U, 32G RAM) it took around 16 minutes for the
error to show up.

Best regards,
Zhihang

On 10/21/25 13:21, 'Heinisch, Alexander' via isar-users wrote:
> Any updates on this patchset? Seems it got lost.
>
> BR Alexander
>
> On Wed, 2025-09-17 at 12:35 +0200, alexander.heinisch@siemens.com
> wrote:
>> From: Alexander Heinisch <alexander.heinisch@siemens.com>
>>
>> By default population of the presets is automatically done by systemd
>> on first-boot.
>>
>> There were several issues with that:
>>
>> 1. The rootfs we get as a build artifact does not reflect the actual
>> system running in the field.
>>
>> 2. For setups without writeable /etc this fails. With that addition
>> it happens already at build time.
>>
>> Note: Additional services are enabled only. Services already enabled
>> during the package installation won't be changed.
>>
>> Opt-out: `ROOTFS_FEATURES:remove = "populate-systemd-preset"`
>>
>> Changes since v2:
>>    - Enable postprocessing to populate systemd presets via
>> ROOTFS_FEATURES
>>
>> Alexander Heinisch (2):
>>    Minor cleanup: Refactor ROOTFS_FEATURES assignment for image to
>> make
>>      upcoming changes more easily trackable.
>>    classes/image-postproc: Enable systemd units based on systemd
>> presets
>>
>>   RECIPE-API-CHANGELOG.md     | 18 ++++++++++++++++++
>>   meta/classes/image.bbclass  | 10 +++++++++-
>>   meta/classes/rootfs.bbclass |  6 ++++++
>>   3 files changed, 33 insertions(+), 1 deletion(-)
>>
>> --
>> 2.39.5
>>

-- 
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 visit https://groups.google.com/d/msgid/isar-users/1dfe2925-928e-4cde-a4ae-42c61a121603%40ilbers.de.