Hi Tyler,

I had tried to reproduce the issue once again. The steps and respective errors are captured as below.

Applied helm chart and operation aborted during processing of horizon.

Horizon pod got crashed.

Horizon pod description.

Pod log command gave below errors.

Both logs are attaching for your reference, please confirm, if I open new bug in launchpad and upload these logs would be fine with you ?

Regards,
Sharath

From: Kumar, Sharath
Sent: Wednesday, October 21, 2020 1:23 PM
To: Smith, Tyler <tyler.smith@windriver.com>; Little, Scott <Scott.Little@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>; Miller, Frank <Frank.Miller@windriver.com>; Bowness, Les <Les.Bowness@windriver.com>; Peters, Matt <Matt.Peters@windriver.com>; Bailey, Henry Albert (Al) <Al.Bailey@windriver.com>
Cc: Kalvala, Haridhar <haridhar.kalvala@intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: FM containerization Build issues

Hi Tyler,

Please find the attached log for your reference.

Regards,
Sharath

From: Smith, Tyler <tyler.smith@windriver.com>
Sent: Saturday, October 17, 2020 12:40 AM
To: Kumar, Sharath <sharath.kumar@intel.com>; Little, Scott <Scott.Little@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>; Miller, Frank <Frank.Miller@windriver.com>; Bowness, Les <Les.Bowness@windriver.com>; Peters, Matt <Matt.Peters@windriver.com>; Bailey, Henry Albert (Al) <Al.Bailey@windriver.com>
Cc: Kalvala, Haridhar <haridhar.kalvala@intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: FM containerization Build issues

Hi,

For issue 1 I would suggest looking into the container logs to see if there are errors being reported when horizon tries starting up. If there’s nothing useful there you could try manually launching horizon from within the container and seeing what the output is. I think that would involve extending the failed container timeouts so that you have enough time to connect and try.

Tyler

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

Hi Frank/Tyler,

Currently issue 1 also blocking us, could you please help us to debug the issue.

Regards,
Sharath

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