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

Custom queries

All open Feature tests
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QAM
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #49031

closed

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

Added by lnussel about 5 years ago. Updated over 3 years 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
Notes
Property changes

Actions

Copy link

Updated by SLindoMansilla about 5 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.

Actions

Copy link

Updated by okurz about 5 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

Actions

Copy link

Updated by mgriessmeier over 4 years ago

Target version changed from Milestone 26 to Milestone 27

to be discussed with jose

Actions

Copy link

Updated by pcervinka over 4 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.

Actions

Copy link

Updated by metan over 4 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.

Actions

Copy link

Updated by pcervinka over 4 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.

Actions

Copy link