[Starlingx-discuss] CentOS7.6 testing status - blocked

[Xie, Cindy]

Thank you, Saul - it's might be possible that the ISO is not consistent with the patch that supposed to be built in. It will be very valuable that Ada continue the testing of the re-built image with the patch cherry-pick in.

Thx. - cindy

-----Original Message-----
From: Saul Wold [mailto:sgw at linux.intel.com] 
Sent: Sunday, February 10, 2019 12:14 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked

Cindy,

I asked Ada to rebuild and re-test based on the patch that Martin provided before CNY, the 20190202 ISO failed the Duplex testing, but when manually patched succeeded.  I wondered if the 20190202 ISO was not rebuilt correctly.

This is why I have not merged Martin's patch yet, I did not find out about this failure mode until Thursday. They started that build on Friday and should be able to test it on Monday.  If your team is back already and can also rebuild with the patch included and confirm it's correct, then we can work to unblock testing of CentOS-76 work.

Sau!


On 2/8/19 6:18 PM, Liu, Yang wrote:
> Correct.
> 
> BR,
> 
> Yang
> 
> *From:*Xie, Cindy [mailto:cindy.xie at intel.com]
> *Sent:* February-08-19 8:28 PM
> *To:* Liu, Yang; starlingx-discuss at 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 at windriver.com]
> *Sent:* Saturday, February 9, 2019 2:09 AM
> *To:* starlingx-discuss at 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 
> <https://bugs.launchpad.net/starlingx/+bug/1814336>
> 
> #1814335 CentOS7.6: Unable to launch vm with UEFI boot 
> <https://bugs.launchpad.net/starlingx/+bug/1814335>
> 
> 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
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss