Regarding https://bugs.launchpad.net/starlingx/+bug/1971981, we believe the main issue is the lack of access in the sanity lab to the public registries; it’s an air-gapped system.  Even though the images are in the private registry, there is a bug in the nginx setup that’s not overriding the registry properly and is still attempting to pull images from the public registries. For those with systems that have public access, you should not be facing this issue.

Investigation is continuing to determine a fix for this issue.

From: Andrei, Bogdan-Iulian <bogdan-iulian.andrei@intel.com>
Sent: Thursday, May 12, 2022 7:57 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220512T035413Z

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

Sanity Test from 2022-May-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220512T035413Z/outputs/iso/)

Status: RED

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

All configurations are affected by these LP bugs: https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready,

https://bugs.launchpad.net/starlingx/+bug/1971981 - nginx-ingress-controller apply-failed during setup of the StarlingX

Kind regards,

Validation team

Andrei Bogdan-Iulian Software Engineer PMCE TEAM Personal Mobile: +40 754905864 bogdan-iulian.andrei@intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania