action #49031: [functional][u][sle][kernel] test to verify kernel-source matches kernel-default - openQA Tests - openSUSE Project Management Tool

action #49031

[functional][u][sle][kernel] test to verify kernel-source matches kernel-default

Added by lnussel about 3 years ago. Updated over 1 year ago.

Status:

Resolved

Priority:

Normal

Assignee:

pcervinka

Category:

New test

Target version:

QE Kernel - QE Kernel Done

Start date:

2019-03-11

Due date:

% Done:

Estimated time:

Difficulty:

Description

Sometimes it happens that kernel-source fails to build but kernel-default succeeds. Both packages need to be in sync though otherwise it's not possible to compile kernel modules, including nvidia, virtualbox etc. So would be nice to have a test that verfies that eg kernel-devel, which is a subpackage of kernel-source matches.

History

#1 Updated by SLindoMansilla about 3 years ago

Subject changed from test to verify kernel-source matches kernel-default to [functional][sle] test to verify kernel-source matches kernel-default

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

#2 Updated by okurz about 3 years ago

Subject changed from [functional][sle] test to verify kernel-source matches kernel-default to [functional][u][sle] test to verify kernel-source matches kernel-default
Target version set to Milestone 26

#3 Updated by mgriessmeier over 2 years ago

Target version changed from Milestone 26 to Milestone 27

to be discussed with jose

#4 Updated by pcervinka over 2 years ago

Subject changed from [functional][u][sle] test to verify kernel-source matches kernel-default to [functional][u][sle][kernel] test to verify kernel-source matches kernel-default
Assignee set to pcervinka
Target version changed from Milestone 27 to 454

Could be planned for next sprint(not now), let's update status after next planning meeting.

#5 Updated by metan over 2 years ago

We do have a LTP tests that are testing basic functionality by building a kernel module, inserting it and then parsing dmesg for tests results, you can have a look at 'testcases/kernel/device-drivers' in LTP source. Such tests would assert, at least partially that kernel-devel is working, unfortunately these tests are not executed on SLES because as far as I can tell we cannot load unsigned modules into the kernel at all, but maybe I haven't looked into the matter deep enough.

#6 Updated by pcervinka over 2 years ago

I guess that primary target is Tumbleweed, as kernel changes are frequent that these glitches can happen.

metan what about to make test (without ltp) based on https://www.tldp.org/LDP/lkmpg/2.6/html/x121.html ?
We can check on openSUSE that module was builded and inserted and on SLES at least that module was builded.