I've created a launchpad to track this issue: https://bugs.launchpad.net/starlingx/+bug/1880248 A better solution is: https://review.opendev.org/730421 An alternative solution is also discussed in https://review.opendev.org/730421. Scott On 2020-05-22 7:50 a.m., chen.dq@neusoft.com wrote:

Temporary Solution: https://review.opendev.org/#/c/730305/:

Analyze the error log below http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200... When compiling, because the "elfutils-libelf-devel" package is not installed in the mock environment. A temporary solution is to upgrade TIS_PATCH_VER related to the kernel in a unified manner to ensure that "elfutils-libelf-devel" is installed in the mock environment.

In theory, "elfutils-libelf-devel" will not be installed in the mock environment. Because kernel modules depend on kernel-devel, kernel depends on elfutils-devel, elfutils-devel depends on elfutils-libelf-devel. So elfutils-libelf-devel must be installed in the mock.

Our local environment 0522 distro build-pkgs is no build error so we cannot  verify this issue.

Best Regards ---------------------- From: Neusoft-team

------------------------------------------------------------------------ *发件人:* build.starlingx@gmail.com <build.starlingx@gmail.com> *发送时间:* 2020年5月22日 10:10:01 *收件人:* starlingx-discuss@lists.starlingx.io *主题:* [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 357 - Failure! Project: STX_build_pre_installer_layered Build #: 357 Status: Failure Timestamp: 20200522T015746Z

Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200... -------------------------------------------------------------------------------- Parameters

MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200522T014731Z DOCKER_BUILD_ID: jenkins-master-distro-20200522T014731Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200... FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200522T014731Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

On 2020-05-24 10:02 p.m., Sun, Austin wrote:

Hi Scott:

     I think adding BuildRequires is definitely need , but I still not fully understand these issues yet.

1) the 20200521 failed at setup issue.

     “It upversioned the kernels, but failed to follow the guidance to upversion all external kmods”

     Does it mean there is no depends check during layer build environment ?

     From my understand , the build system should solve dependence automatically and re-build necessary dependent packages.

Yes, that was the intent, but this dependence mechanism seems to be having issues that I need to get to the bottom of.  I'll be opening a launchpad once I know a bit more.

2) Build # 357 - Failure!

     Does CENGN distro layer clean build ?

     In local layer build verify , as guidance , doing clean build,  this issue can not be reproduced.

since kmod will depend on kernel,  once kernel build , the elfutils-libelf-devel should be installed in mock env.

Any suggestion to verify this issue on local environment to avoid similar issue happen in future ?

layered build is using build avoidance.  We were forced to do this because a clean room build of an unchanged src.rpm still shows deltas in the rpms (trivial stuff like timestamps on files) that would force everyone to re-download those rpms after every build.  This would totally defeat the advantages layered build hoped to offer. Build avoidance just re-uses a prior build of a given rpm if the change/dependency check doesn't flag it as requiring a rebuild.

Thanks.

BR Austin Sun.

*From:*Scott Little <scott.little@windriver.com> *Sent:* Saturday, May 23, 2020 6:18 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] 答复: [build-report] STX_build_pre_installer_layered - Build # 357 - Failure!

I've created a launchpad to track this issue:

https://bugs.launchpad.net/starlingx/+bug/1880248

A better solution is:

https://review.opendev.org/730421

An alternative solution is also discussed in https://review.opendev.org/730421 <https://review.opendev.org/730421>.

Scott

On 2020-05-22 7:50 a.m., chen.dq@neusoft.com <mailto:chen.dq@neusoft.com> wrote:

Temporary Solution:

https://review.opendev.org/#/c/730305/:

Analyze the error log below

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200...

When compiling, because the "elfutils-libelf-devel" package is not installed in the mock environment. A temporary solution is to upgrade TIS_PATCH_VER related to the kernel in a unified manner to ensure that "elfutils-libelf-devel" is installed in the mock environment.

In theory, "elfutils-libelf-devel" will not be installed in the mock environment. Because kernel modules depend on kernel-devel, kernel depends on elfutils-devel, elfutils-devel depends on elfutils-libelf-devel. So elfutils-libelf-devel must be installed in the mock.

Our local environment 0522 distro build-pkgs is no build error so we cannot  verify this issue.

Best Regards

----------------------

From: Neusoft-team

------------------------------------------------------------------------

*发件人**:* build.starlingx@gmail.com <mailto:build.starlingx@gmail.com> <build.starlingx@gmail.com> <mailto:build.starlingx@gmail.com> *发送时间**:* 2020年5月22日 10:10:01 *收件人**:* starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> *主题**:* [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 357 - Failure!

Project: STX_build_pre_installer_layered Build #: 357 Status: Failure Timestamp: 20200522T015746Z

Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200... -------------------------------------------------------------------------------- Parameters

MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200522T014731Z DOCKER_BUILD_ID: jenkins-master-distro-20200522T014731Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200... FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200522T014731Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false

--------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

_______________________________________________

Starlingx-discuss mailing list

Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>

http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss