action #53660
closed[functional][u] test fails in kdump_and_crash: Not compatible with kernel-default-base
0%
Description
Observation¶
Looks like there's a problem detecting properly the name of the kernel package.
Suggestions¶
** Take a look at lib/kdump_utils.pm L26 and figure out why the condition is not met.
openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
kdump_and_crash
Test suite description¶
Same as jeos, plus some more tests.
Reproducible¶
Fails since (at least) Build 20190311
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla about 4 years ago
- Subject changed from test fails in kdump_and_crash: Not compatible with kernel-default-base to [functional][u] test fails in kdump_and_crash: Not compatible with kernel-default-base
- Priority changed from Normal to High
Updated by szarate about 4 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by jorauch about 4 years ago
- Status changed from Workable to In Progress
Updated by jorauch about 4 years ago
is_jeos() && (!is_opensuse() && !check_var('ARCH', 'aarch64')) ? 'kernel-default-base' : 'kernel-default';
As it is executed on opensuse it has to fail, sadly I do not know under which conditions which kernel shall be selected
Updated by jorauch about 4 years ago
- Status changed from In Progress to Feedback
Updated by jorauch about 4 years ago
PR merged, waiting for verification in production
Updated by SLindoMansilla about 4 years ago
- Has duplicate action #55325: [qam] test fails in kdump_and_crash - name of package wrongly determined added
Updated by SLindoMansilla about 4 years ago
For the record: affecting QAM tests https://openqa.suse.de/tests/3230551#step/kdump_and_crash/138
Updated by jorauch about 4 years ago
Created:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8174
to fix broken tests, seems good so far
Updated by jorauch about 4 years ago
- Status changed from Feedback to Resolved
Not broken so far, considering it as resolved