Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side.

We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle?

Thanks! Cindy 

Hi Cindy,

 

We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail.

We need the grubx64.efi to be readable by others as well.

 

../pxeboot/EFI/

total 1220

drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 .

drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 ..

drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 centos

-rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi

 

The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi.

For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong).

 

BR,

Yang

 

From: Liu, Yang
Sent: February-12-19 9:00 AM
To: 'Xie, Cindy'; starlingx-discuss@lists.starlingx.io; Cabrales, Ada; Waheed, Numan
Subject: RE: CentOS7.6 testing status - blocked

 

Thanks Cindy. Will do.

 

BR,

Yang

 

From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: February-11-19 8:10 PM
To: Liu, Yang; starlingx-discuss@lists.starlingx.io; Cabrales, Ada; Waheed, Numan
Subject: RE: CentOS7.6 testing status - blocked

 

Hi, Numan/Yang,

The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing.

 

Thx. - cindy

 

From: Liu, Yang [mailto:yang.liu@windriver.com]
Sent: Saturday, February 9, 2019 10:18 AM
To: Xie, Cindy <cindy.xie@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: CentOS7.6 testing status - blocked

 

Correct.

 

BR,

Yang

 

From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: February-08-19 8:28 PM
To: Liu, Yang; starlingx-discuss@lists.starlingx.io
Subject: RE: CentOS7.6 testing status - blocked

 

Hi, Yang,

Thanks for the report.

Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well.

 

Th.x - cindy

 

From: Liu, Yang [mailto:yang.liu@windriver.com]
Sent: Saturday, February 9, 2019 2:09 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked

 

Hi folks,

 

Here’s an update for CentOS7.6 testing.

We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360)

We will continue after that issue is resolved.

 

System	NICs Mgmt;infra;data	Special Configs	Test coverage after Install and Config	Status/Issues
Dedicated storage	X540-AT2; X540-AT2; fortville	IPv6	Sanity, nova	Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot
One node system	none; none; X522/X577-AT		Sanity, basic regression	Completed. Passed.
Two node system	fortville; fortville; fortville	tboot, tpm, https, extended security profile	Sanity, security	Blocked by #1814360
Multi-node system	BCM5720; Niantic; Niantic	Sriov(niantic),pcipt(niantic)	Sanity, networking	Completed. Passed.
Two node system	Fortville; none; Fortville	Low latency, UEFI	Sanity, basic regression, cyclictest	Blocked by #1814360
Two node system	Fortville; none; Fortville	Secure boot	Sanity, security	Blocked by #1814360
Multi-node system	I350; Niantic/cx3; cx3	Pxeboot script	Sanity	Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic.
??	CX4 on infra or mgmt, but NOT data			Won’t test. We don’t have a system have required nics.

 

BR,

yang