[OE-core] [PATCH] image: Fix "metadata is not deterministic" when chaining 2+ CONVERSION_CMDs

[Martin Hundebøll]

On 2017-09-15 20:20, Martin Hundebøll wrote:
> On 2017-09-15 14:16, Tom Rini wrote:
>>> This commit has resulted in more or less persistent basehash issues
>>> for my cpio.gz.u-boot image:
>>>
>>> ERROR: When reparsing 
>>> /home/mnhu/projects/pil/yocto/meta-pil/recipes-filesystems/rescue-rootfs.bb.do_image_cpio, 
>>>
>>> the basehash value changed from ac9907bbb8ee2ee6d9ca90f7a7e265f5 to
>>> 8c7b717add6b1d1ba6ff761ebfdedf01. The metadata is not deterministic
>>> and this needs to be fixed.
>>>
>>> The error occurs repeatedly when doing `bitbake -c clean
>>> rescue-rootfs && bitbake rescue-rootfs`. Reverting the commit makes
>>> the error go away.
>>>
>>> Also, the issue only appears for cpio.gz.u-boot image types, but not
>>> for cpio.gz
>>>
>>> I am far from an expert in bitbake signature handling, so please let
>>> me know what to do, to debug this further.
>> Can you let me know what layers and machine I need to reproduce this?
>> I'll take a look, thanks!
> 
> I am able to reproduce with the following:
> 
>    - Ubuntu 16.04 based on the attached Dockerfile
>    - A clean clone of poky (commit 072430b9b3)
>    - meta, meta-poky, and meta-yocto-bsp (see build-config.log)
>    - beaglebone machine and gpio.gz.u-boot image type (see local.conf)

Sorry, this seems to be caused by your earlier patch: 88eec32150 
('image.bbclass: Correct chaining compression support'). My first 
conclusion was probably caused by caching playing me a trick.

I'll reply to that patch instead.

// Martin