[Starlingx-discuss] FM containerization Build issues

Mukherjee, Sanjay K sanjay.k.mukherjee at intel.com
Fri Oct 16 11:04:08 UTC 2020


Hi Scott,
I have added the following bug :- https://bugs.launchpad.net/starlingx/+bug/1900126

With the requested log. Please verify and let me know any further details is required



Thanks and Regards,
Sanjay Mukherjee

From: Scott Little <scott.little at windriver.com>
Sent: Thursday, October 15, 2020 8:50 PM
To: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com>; Miller, Frank <Frank.Miller at windriver.com>; Bowness, Les <Les.Bowness at windriver.com>; Peters, Matt <Matt.Peters at windriver.com>; Bailey, Henry Albert (Al) <Al.Bailey at windriver.com>; Smith, Tyler <tyler.smith at windriver.com>
Cc: Kumar, Sharath <sharath.kumar at intel.com>; Kalvala, Haridhar <haridhar.kalvala at intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: Re: FM containerization Build issues


Re Issue 2

Have you failed a launchpad?

Please include ALL steps required to reproduce your build issue including setting environment variables, checking out source code (including how to cherry pick any of your changes), setting up docker, etc... and point out which command hung.

Include the content of your localrc and buildrc

Not knowing where you hung, it's hard to comment on which specific log would be most relevant.

Based on your attachment, perhaps it was build-stx-images.sh? In that case it would likely be one of the logs matching the pattern...

    ${MY_WORKSPACE}/std/build-images/docker-${LABEL}-${OS}-${BUILD_STREAM}.log

i.e. there is a separate log for each image.

You can pass the '--only <LABEL>' arg to build-stx-images.sh to speed up reproduction of the issue.

Catpuring and attaching the console/terminal session is also a good idea

Scott


On 2020-10-15 12:48 a.m., Mukherjee, Sanjay K wrote:
HI Frank/Tyler/Scott
  As discussed in the containerization meeting sharing the build issues details  need your inputs :-


  *   Issue 1:- FM with Mario's changes throws horizon not ready error on 4.0 release onwards  . Attaching the Armada log for reference .

     *   Please let us know where else to look for to get more details of the issue
     *   Need your inputs to move forward

  *   Issue 2:- Docker build on the latest master branch is hanging, let us know if this is a known issue . Let us know if any specific log is needed
  *   Issue 3:- Presence of only python 3  packages in the wheels tar. It  causes issue while building in Python 2.7 environment

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/stx-centos-stable-wheels.tar

We built using python 2.7 taking the wheel packages built locally. (docker_build_script_2.txt)

I have attached the logs and the docker scripts . Please let us know if any further details are needed.






Thanks and Regards,
Sanjay Mukherjee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20201016/8287069b/attachment-0001.html>


More information about the Starlingx-discuss mailing list