In Yocto mender-artifact has QA issues

Hi all,

Installing mender-artifact on the target image and into the SDK during Yocto build results in QA issues.

mender-artifact installed to the target image by:

IMAGE_INSTALL:append = " mender-artifact"

Native mender-artifact installed to the SDK by:

TOOLCHAIN_HOST_TASK:append = " nativesdk-mender-artifact"

QA issues are textrel and buildpaths.

ERROR: mender-artifact-4.1.0-r0 do_package_qa: QA Issue: File /usr/bin/mender-artifact in package mender-artifact contains reference to TMPDIR [buildpaths]

ERROR: mender-artifact-4.1.0-r0 do_package_qa: QA Issue: mender-artifact: ELF binary /usr/bin/mender-artifact has relocations in .text [textrel]

ERROR: mender-artifact-4.1.0-r0 do_package_qa: QA Issue: File /usr/bin/.debug/mender-artifact in package mender-artifact-dbg contains reference to TMPDIR [buildpaths]

ERROR: mender-artifact-4.1.0-r0 do_package_qa: Fatal QA errors were found, failing task.

ERROR: Logfile of failure stored in: /yocto/tmp/work/corei7-64-poky-linux/mender-artifact/4.1.0/temp/log.do_package_qa.81296

ERROR: Task (/yocto/VMS.XI.Yocto/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_4.1.0.bb:do_package_qa) failed with exit code ‘1’

NOTE: Tasks Summary: Attempted 9016 tasks of which 8070 didn’t need to be rerun and 1 failed.

For those who are facing the same issue, it can be circumvent by skipping those specific QA steps by adding the recipes-mender/mender-artifact/mender-artifact_%.bbappend file to your layer with the following content:

INSANE_SKIP:append = " buildpaths textrel"

These Yocto QA checks usually detect real or potential problems, it would be great to find and fix the original root-case in mender-artifact codebase. Thanks in advance.

Best regards,

Zsolt Tomis

1 Like

Hi @zsolt.tomis,

Thanks for stepping up! Yeah I will definitely try to find the reason - my gut feeling is "something with golang":grimacing:

But anyways putting mender-artifact onto a Yocto-built image is a rare requirement, so one day I’d love to hear about your use case.

Greetz,
Josef