Bug 10067

Summary:	Host sanity check fails for CentOS 7
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Bill Randle <bill.randle>
Component:	core	Assignee:	Jose Perez C <jose.perez.carranza>
Status:	RESOLVED FIXED	QA Contact:	David Rodriguez <david.israelx.rodriguez.castellanos>
Severity:	normal
Priority:	Medium+	CC:	bluelightning, meta.mr.watcher, meta.watcher, randy.macleod, sgw, yi.zhao
Version:	2.2
Target Milestone:	2.2 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Bill Randle 2016-08-02 20:20:51 UTC

sanity.conf includes a list of test distros in the variable SANITY_TESTED_DISTROS that have been validated for builds. One of the entries in the list is "CentOS-7.*" However, I still see warning messages on the AB:
  "WARNING: Host distribution "CentOSLinux-7.2.1511" has not been validated..."

The distro id is figured out by meta/lib/oe/lsb.py based first on the output of the 'lsb_release' command, or if not present, then parsing some known files, such as /etc/redhat-release. In the case of CentOS 7, /etc/redhat-release contains "CentOS Linux release 7.2.1511 (Core)". This parsed as "CentOS Linux" (id) and "7.2.1511" (release).

Further down in the code, it deletes all non-alphanumeric characters in the id, which compresses it to "CentOSLinux", without the space.

So, bottom line, the "CentOS-7.*" entry in the sanity list should be replaced with "CentOSLinux-7.*".

Other distributions should be checked to see if the id string contains a (collapsed) space and adjust the sanity list name accordingly.

In addition, I noticed the supported Yocto released are included in the sanity list, but 2.1 is missing. Should it be added to the list?

Comment 1 Paul Eggleton 2016-08-02 20:30:50 UTC

I'm receiving the same warning on CentOS 7 here.

Yes we should add the 2.1 release and 2.2 (and drop unsupported older versions) - those are there for the build appliance. This was something that the QA team were supposed to be doing for every release, along with updating the other distributions in the list - though it doesn't matter who actually does it as long as it gets done.

Comment 2 Bill Randle 2016-08-02 20:34:02 UTC

Jose Perez Carranza volunteered to fix it up.

Comment 3 Jose Perez C 2016-08-02 20:36:53 UTC

This was a process that was not clearly defined in the past but now is defined an documented here https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan , I will investigate if another OS distributions are giving the same warning and update the list accordingly.

Comment 4 Jose Perez C 2016-08-03 17:23:18 UTC

(In reply to comment #1)
> I'm receiving the same warning on CentOS 7 here.
> 
> Yes we should add the 2.1 release and 2.2 (and drop unsupported older
> versions) - those are there for the build appliance. This was something that
> the QA team were supposed to be doing for every release, along with updating
> the other distributions in the list - though it doesn't matter who actually
> does it as long as it gets done.

2.2 should be added? or this should be added until is officially released ?

Comment 5 Paul Eggleton 2016-08-03 20:20:45 UTC

I don't think it does harm to add it in advance - but the most important thing is it gets added in time for the release.

Comment 6 Yi Zhao 2016-08-04 02:16:36 UTC

(In reply to comment #1)
> I'm receiving the same warning on CentOS 7 here.
> 
> Yes we should add the 2.1 release and 2.2 (and drop unsupported older
> versions) - those are there for the build appliance. This was something that
> the QA team were supposed to be doing for every release, along with updating
> the other distributions in the list - though it doesn't matter who actually
> does it as long as it gets done.

(In reply to comment #4)
> (In reply to comment #1)
> > I'm receiving the same warning on CentOS 7 here.
> > 
> > Yes we should add the 2.1 release and 2.2 (and drop unsupported older
> > versions) - those are there for the build appliance. This was something that
> > the QA team were supposed to be doing for every release, along with updating
> > the other distributions in the list - though it doesn't matter who actually
> > does it as long as it gets done.
> 
> 2.2 should be added? or this should be added until is officially released ?

Please add Poky-2.1 in the list and backport to krogoth branch. There is a warning in build appliance for krogoth

Comment 7 Jose Perez C 2016-08-04 20:22:58 UTC

Patch sent to the mailing list 

https://lists.yoctoproject.org/pipermail/poky/2016-August/010643.html

Comment 8 Jose Perez C 2016-08-10 13:05:13 UTC

Patch is now in master on below commit: 

http://git.yoctoproject.org/clean/cgit.cgi/poky/commit/?id=dd53025d24ef7ab948414cc0141f65f48eaacfa2