When building the first time an image via Hob, I run into the following error: DEBUG: Executing python function do_bootdirectdisk DEBUG: Executing python function build_syslinux_cfg DEBUG: Python function build_syslinux_cfg finished DEBUG: Executing python function build_efi_cfg DEBUG: Python function build_efi_cfg finished DEBUG: Executing shell function build_boot_dd ERROR: /home/yocto/Workspace/lteagg/poky/build/tmp/deploy/images/genericx86-64/core-image-minimal-initramfs-genericx86-64.cpio.gz is invalid. initrd image creation failed. WARNING: exit code 1 from a shell command. DEBUG: Python function do_bootdirectdisk finished ERROR: Function failed: build_boot_dd (log file is located at /home/yocto/Workspace/lteagg/poky/build/tmp/work/genericx86_64-poky-linux/core-image-full-cmdline/1.0-r0/temp/log.do_bootdirectdisk.13554) However, when I generate the same image again without any changes it builds fine. I have made no changes at all to any recipes or configuration. I had selected ext3, hddimg, and vmdk as image types in Advance configuration.
I was able to reproduce this with HOB and standalone, there appears to be a dependency issue, will investigate further,
Padam, It may be the case that live and vmdk are not compatible image types, meaning that they can not be built at the same time, the reason it may have worked the second time is that it built the initramfs and the timing of the dependencies and built images worked. There is another bug noting this issue and adding a sanity test to the core to prevent this situation. If you don't believe this is correct or you have a different issue, please re-open this bug and explain the failure and your needs. *** This bug has been marked as a duplicate of bug 6889 ***
(In reply to comment #2) > Padam, It may be the case that live and vmdk are not compatible image types, > meaning that they can not be built at the same time, the reason it may have > worked the second time is that it built the initramfs and the timing of the > dependencies and built images worked. There is another bug noting this > issue > and adding a sanity test to the core to prevent this situation. If you > don't > believe this is correct or you have a different issue, please re-open this > bug > and explain the failure and your needs. > > *** This bug has been marked as a duplicate of bug 6889 *** Verified as per above comments.