Hi Alex:

For this LP #1926029  , since there are not compute-0 log in logs uploaded,  

Would you like to force lock compute-0 ,  and ssh to compute-0 , and collect the log from compute-0 ,  and upload to LP  for triage issue ?

 

Thanks.

BR
Thanks.

 

 

From: Dimofte, Alexandru <alexandru.dimofte@intel.com>
Sent: Tuesday, April 27, 2021 5:21 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210427T040435Z

 

Sanity Test from 2021-April-27 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210427T040435Z/outputs/iso/ )

 

Status: RED

 

This image is affected by:

https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry

Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful.

Critical alarm Id: 200.011 - compute-0 experienced a configuration failure.

 

OBS: This issue is observed only on MASTER branch (RC 5.0 is not affected).

 

Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210427T040435Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz

 

Regards,

Alexandru Dimofte

 

  Logo

Description automatically generated

Dimofte Alexandru

Software Engineer

STARLINGX TEAM

Skype no: +40 336403734

Personal Mobile: +40 743167456

alexandru.dimofte@intel.com

Intel Romania