meta-rauc-qemux86/recipes-bsp/boot-image/boot-image.bb:do_deploy FAILED

[matthiasklein]

With the latest master/kirkstone branch the build fails in the boot-image.bb recipe:

ERROR: boot-image-1.0-r0 do_deploy: ExecutionError('/home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/temp/run.do_deploy.3207517', 1, None, None)
ERROR: Logfile of failure stored in: /home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/temp/log.do_deploy.3207517
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['/home/mak/kas-rauc-community/poky/meta/recipes-devtools/gcc/gcc-cross_11.2.bb:do_populate_sysroot', '/home/mak/kas-rauc-community/poky/meta/recipes-devtools/gcc/gcc-runtime_11.2.bb:do_populate_sysroot', 'virtual:native:/home/mak/kas-rauc-community/poky/meta/recipes-devtools/mtools/mtools_4.0.38.bb:do_populate_sysroot', 'virtual:native:/home/mak/kas-rauc-community/poky/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot', 'virtual:native:/home/mak/kas-rauc-community/poky/meta/recipes-devtools/dosfstools/dosfstools_4.2.bb:do_populate_sysroot', 'virtual:native:/home/mak/kas-rauc-community/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', '/home/mak/kas-rauc-community/poky/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot', '/home/mak/kas-rauc-community/poky/meta/recipes-core/glibc/glibc_2.35.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['mtools-native', 'dosfstools-native']
| NOTE: Skipping as already exists in sysroot: ['gcc-cross-x86_64', 'gcc-runtime', 'patch-native', 'pseudo-native', 'quilt-native', 'glibc', 'linux-libc-headers', 'libtool-native', 'binutils-cross-x86_64', 'zlib-native', 'texinfo-dummy-native', 'flex-native', 'xz-native', 'mpfr-native', 'gmp-native', 'libmpc-native', 'gnu-config-native', 'libgcc', 'attr-native', 'gettext-minimal-native', 'm4-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| mkfs.fat 4.2 (2021-01-31)
| mv: cannot move '/home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/efi-boot.vfat' to '/home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/deploy-boot-image/': Not a directory
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/mak/kas-rauc-community/meta-rauc-demo/meta-rauc-qemux86/recipes-bsp/boot-image/boot-image.bb:do_deploy) failed with exit code '1'

To get to this point I had to add kirkstone to the compatible layers at: https://github.com/rauc/meta-rauc-community/blob/master/meta-rauc-qemux86/conf/layer.conf#L13

[matthiasklein]

@leon-anavi @ejoerns Do you have an idea how to fix this?

[ejoerns]

To me, it looks like DEPLOYDIR (i.e. /home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/deploy-boot-image/) is not created. But haven't checked this with an actual build, yet.

Might be related to

https://git.yoctoproject.org/poky/commit/meta/classes/deploy.bbclass?id=a0f76ba08e657f9d1df5a00d743adeae840074c4

but how I understand the cleandirs handling, this should not break anything.

[matthiasklein]

Yes, the DEPLOYDIR is missing:

$ ls -l /home/mak/kas-rauc-community/build/tmp/work/core2-64-poky-linux/boot-image/1.0-r0/
total 736
drwxr-xr-x 2 mak mak     4096 Mar 25 06:58 boot-image-1.0
-rw-r--r-- 1 mak mak       65 Mar 25 09:01 configure.sstate
drwxr-xr-x 2 mak mak     4096 Mar 25 06:59 deploy-source-date-epoch
drwxr-xr-x 3 mak mak     4096 Mar 25 09:20 efi-boot
-rw-r--r-- 1 mak mak 33572864 Mar 25 09:20 efi-boot.vfat
drwxr-xr-x 5 mak mak     4096 Mar 25 09:20 recipe-sysroot
drwxr-xr-x 7 mak mak     4096 Mar 25 09:01 recipe-sysroot-native
drwxr-xr-x 2 mak mak     4096 Mar 25 06:58 source-date-epoch
drwxr-xr-x 2 mak mak     4096 Mar 25 09:20 temp

[leon-anavi]

@matthiasklein, the pull request by @ejoerns has been merged. Thank you both for reporting and fixing the issue.

[matthiasklein]

@ejoerns Thank you very much for fixing the bug!