Bug 7454

Summary:	core-image-full-cmdine build failure, error in bootdirectdisk
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Padam Jeet Singh <padam.singh>
Component:	meta-yocto	Assignee:	Saul Wold <sgw>
Status:	VERIFIED DUPLICATE	QA Contact:	Alexandru Georgescu <alexandru.c.georgescu>
Severity:	critical
Priority:	Medium+	CC:	alexandru.c.georgescu, poky.bs.watcher, poky.watcher, sgw
Version:	1.7.1
Target Milestone:	1.8 M4
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Padam Jeet Singh 2015-03-13 05:10:28 UTC

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.

Comment 1 Saul Wold 2015-03-19 05:08:45 UTC

I was able to reproduce this with HOB and standalone, there appears to be a dependency issue, will investigate further,

Comment 2 Saul Wold 2015-03-20 15:26:07 UTC

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 ***

Comment 3 Alexandru Georgescu 2015-03-26 06:46:52 UTC

(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.