Bug 11819

Summary: multiubi and container rootfs is not being created
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Jose Perez C <jose.perez.carranza>
Component: coreAssignee: Ed Bartosh <eduard.bartosh>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher
Version: 2.4   
Target Milestone: 2.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 10745    

Description Jose Perez C 2017-07-21 13:32:25 UTC
when using IMAGE_FSTYPES += " multiubi" the "*.rootfs.multiubi" file is not being created. 

Steps: 

1. Add the following variables to "conf/local.conf"
IMAGE_FSTYPES += "multiubi"
2. Compile
$ bitbake core-image-minimal

Expected result:
The compilation process should be performed successfully and the generated compressed image should be at: "build/tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.multiubi"

Actual result:
The compilation image process is completed successfully but "build/tmp/deploy/images/<MACHINE>/core-image-minimal-<MACHINE>.multiubi" is not being created. 


NOTE:
multiubi is listed as a valid image type by: 

    $ bitbake -e core-image-minimal |grep ^IMAGE_TYPES=
Comment 1 Jose Perez C 2017-07-21 14:06:46 UTC
Also apply when using IMAGE_FSTYPES += "container",  the "*.rootfs.container" file is not being created.
Comment 2 Ed Bartosh 2017-07-28 10:47:58 UTC
1. More additions to local.conf are required to produce multiubi image

Here is an example:

IMAGE_FSTYPES += "multiubi"
MULTIUBI_BUILD ?= "normal large"
export MKUBIFS_ARGS_normal = "-F -m 2048 -e 124KiB -c 1912 -x zlib"
export UBINIZE_ARGS_normal = "-m 2048 -p 128KiB -s 2048"
export MKUBIFS_ARGS_large = "-F -m 4096 -e 248KiB -c 8124 -x zlib"
export UBINIZE_ARGS_large = "-m 4096 -p 256KiB -s 4096"

with above 6 lines in local.conf 'bitbake core-image-minimal' produces set of expected images just fine:

$ ls -la tmp/deploy/images/qemux86-64/ |grep ubi
-rw-r--r-- 2 ed users  8126464 Jul 28 13:12 core-image-minimal-qemux86-64-20170728093839_large.rootfs.ubi
-rw-r--r-- 2 ed users  7364608 Jul 28 13:12 core-image-minimal-qemux86-64-20170728093839_large.rootfs.ubifs
-rw-r--r-- 2 ed users  6422528 Jul 28 13:12 core-image-minimal-qemux86-64-20170728093839_normal.rootfs.ubi
-rw-r--r-- 2 ed users  5967872 Jul 28 13:12 core-image-minimal-qemux86-64-20170728093839_normal.rootfs.ubifs
lrwxrwxrwx 2 ed users       61 Jul 28 13:12 core-image-minimal-qemux86-64_large.ubi -> core-image-minimal-qemux86-64-20170728093839_large.rootfs.ubi
lrwxrwxrwx 2 ed users       63 Jul 28 13:12 core-image-minimal-qemux86-64_large.ubifs -> core-image-minimal-qemux86-64-20170728093839_large.rootfs.ubifs
lrwxrwxrwx 2 ed users       62 Jul 28 13:12 core-image-minimal-qemux86-64_normal.ubi -> core-image-minimal-qemux86-64-20170728093839_normal.rootfs.ubi
lrwxrwxrwx 2 ed users       64 Jul 28 13:12 core-image-minimal-qemux86-64_normal.ubifs -> core-image-minimal-qemux86-64-20170728093839_normal.rootfs.ubifs
-rw-r--r-- 2 ed users      289 Jul 28 13:12 ubinize_large-core-image-minimal-qemux86-64-20170728093839.cfg
-rw-r--r-- 2 ed users      290 Jul 28 13:12 ubinize_normal-core-image-minimal-qemux86-64-20170728093839.cfg


2. My guess is that building container images doesn't produce rootfs.container. This is covered by containerimage test which passes on current master:

$ oe-selftest -r containerimage
2017-07-28 13:22:40,790 - oe-selftest - INFO - Adding layer libraries:
2017-07-28 13:22:40,790 - oe-selftest - INFO - 	/home/ed/git/yocto/poky/meta/lib
2017-07-28 13:22:40,791 - oe-selftest - INFO - 	/home/ed/git/yocto/poky/meta-yocto-bsp/lib
2017-07-28 13:22:40,791 - oe-selftest - INFO - 	/home/ed/git/yocto/poky/meta-selftest/lib
2017-07-28 13:22:40,792 - oe-selftest - INFO - Running bitbake -p
2017-07-28 13:23:32,153 - oe-selftest - INFO - test_expected_files (containerimage.ContainerImageTests) ... ok
2017-07-28 13:23:32,154 - oe-selftest - INFO - 
2017-07-28 13:23:32,154 - oe-selftest - INFO - ----------------------------------------------------------------------
2017-07-28 13:23:32,154 - oe-selftest - INFO - Ran 1 test in 38.096s
2017-07-28 13:23:32,154 - oe-selftest - INFO - 
2017-07-28 13:23:32,154 - oe-selftest - INFO - OK
2017-07-28 13:23:32,154 - oe-selftest - INFO - RESULTS:
2017-07-28 13:23:32,154 - oe-selftest - INFO - RESULTS - containerimage.ContainerImageTests.test_expected_files - Testcase 1619: PASSED
2017-07-28 13:23:32,155 - oe-selftest - INFO - SUMMARY:
2017-07-28 13:23:32,155 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 38.096s
2017-07-28 13:23:32,155 - oe-selftest - INFO - oe-selftest - OK - All required tests passed

Please, look at the test case to get more details.

NOTE: This looks like 2 absolutely unrelated issues to me and shouldn't be put in one bug. Please, consider to create one bug per issue next time.