Hi again Ghada,

I think I found the fix.

Some time ago because of this issue: https://bugs.launchpad.net/starlingx/+bug/1949771

I created this commit: https://review.opendev.org/c/starlingx/test/+/818131 which was merged on master branch but never cherry-picked on r/stx.6.0 branch.

I’m testing now locally if this will fix the issue on stx.6.0. If so,  I will create the needed change(s). I’ll try to be quick.

Thanks!

Alex

From: Dimofte, Alexandru
Sent: Tuesday, January 25, 2022 3:57 PM
To: Khalil, Ghada <Ghada.Khalil@windriver.com>; starlingx-discuss@lists.starlingx.io
Cc: Church, Robert <Robert.Church@windriver.com>; Miller, Frank <Frank.Miller@windriver.com>
Subject: RE: [Starlingx-discuss] Sanity RC.6.0 Test LAYERED build ISO 20220119T184201Z

Hi Ghada,

I triggered again the Standard and Standard Ext bare-metal + virtual for stx.6.0.

I remember that last time I tried 6 times on Standard bare-metal, always seeing this issue. For master(layered) builds I am using master branch and for StaringX6.0 I am using r/stx.6.0 branch(I will compare today and check the diffs).

What I can tell is that before adding the OSDs in the Provision.robot is checked if all hosts are ready(both controllers are unlocked, both computes are LOCKED, this is why the Simplex and Duplex are fine).

Then checking why the computes are locked I observed that in the unlock computes function it waits 30mins for platform-integ-apps to be APPLIED.

On Standard and Standard Ext the platform-integ-apps remained in uploaded state and not applied. I checked after few hours ant it was still on uploaded state.

I will check again today and hopefully I will find any clue...

Br,

Alex

From: Khalil, Ghada <Ghada.Khalil@windriver.com>
Sent: Monday, January 24, 2022 11:39 PM
To: Dimofte, Alexandru <alexandru.dimofte@intel.com>; starlingx-discuss@lists.starlingx.io
Cc: Church, Robert <Robert.Church@windriver.com>; Miller, Frank <Frank.Miller@windriver.com>
Subject: RE: [Starlingx-discuss] Sanity RC.6.0 Test LAYERED build ISO 20220119T184201Z

Hi Alex,

Can you please try the stx.6.0 sanity again?  It would be good to get more information about how intermittent the issue reported below is.

From the comments in the LP from Bob Church (who reviewed the LP logs), it appears that the sanity suite is perhaps checking the app state too early.  Is there a difference in the sanity steps executed for stx.6.0 and stx master?  There shouldn’t be much difference between the two branches in relation to the platform-integ-apps, so it’s surprising that we are hitting this issue on one branch and not the other.

Thanks,

Ghada

From: Dimofte, Alexandru <alexandru.dimofte@intel.com>
Sent: Friday, January 21, 2022 6:17 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Sanity RC.6.0 Test LAYERED build ISO 20220119T184201Z

[Please note: This e-mail is from an EXTERNAL e-mail address]

Sanity Test from 2022-January-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20220119T184201Z/outputs/iso/)

Status: RED

 
Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20220119T184201Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz

Standard configuration and sporadically standard ext configuration on bare-metal and virtual setups are affected by:

https://bugs.launchpad.net/starlingx/+bug/1958630 - platform-integ-apps booting != completed or uploaded != applied issues

Kind regards,

Alexandru Dimofte

Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte@intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania