Hi Anton,

I haven't had a chance to try the patch you mentioned yet.
But this fix has greatly reduced the error frequency on our side.

As Cedric mentioned, we also have managed servers and several IT services that might cause such issues.
That's why, I can say that we have achieved acceptable stability for now.

Thanks,
Gokhan

On Tuesday, August 6, 2024 at 11:02:55 AM UTC+3 Anton Mikanovich wrote:
12/07/2024 10:04, Anton Mikanovich wrote:
> Hello Gökhan,
>
> I've found an issue with isar-apt usage without lock protection in
> deb_dl_dir_export and imager_run implementations. This can influence
> on umount
> issues you've observed, so please try the fix from patchset:
>
> [PATCH 0/2] Protect isar-apt usages in shell

Unfortunately this fix didn't help.
Even with it we've got the same issue (it looks like there is the first time
we've catched it in our CI):

ERROR: Task
(mc:qemuarm-bullseye:/workspace/build-auto/isar_next/1324/meta-test/recipes-core/images/isar-image-ci.bb:do_image_ext4)
failed with exit code '1'
E: 10mount: umount:
/run/schroot/mount/isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3:
target is busy.
E: 10mount: rmdir: failed to remove
'/var/run/schroot/mount/isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3':
Device or resource busy
E:
isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3:
Chroot setup failed: stage=setup-stop

--
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/f9dac9c3-e29e-4093-a3c0-18f01e5317c2n%40googlegroups.com.