action #71461
open[opensuse] test fails in zfs - zfs kernel module not found on Jump
0%
Description
Observation¶
openQA test in scenario opensuse-Jump:15.2-DVD-x86_64-extra_tests_filesystem@64bit fails in
zfs
Test suite description¶
Maintainer: okurz@suse.de
Filesystem related tests, for example snapper and btrfs features.
Reproducible¶
Fails since (at least) Build 75.1
Expected result¶
Last good: 73.7 (or more recent)
Further details¶
Always latest result in this scenario: latest
If there is no zfs kernel module built for SLE, then zfs module should not available for Jump as well.
Updated by tjyrinki_suse over 3 years ago
- Subject changed from test fails in zfs - zfs kernel module not found on Jump to [qe-core][opensuse] test fails in zfs - zfs kernel module not found on Jump
Updated by ph03nix over 3 years ago
Yeah, I was just looking into this and the problem is that there are no builds for Jump/Leap 15.3 available: https://build.opensuse.org/repositories/filesystems/zfs
I'm improving the output of the zfs test module right now. I want to make it more obvious that this is the reason for the test module failure. Apart from that there is little that we can do from the openQA side, until builds for 15.3 become available.
Working on https://progress.opensuse.org/issues/81266 atm - Improved output of zfs test failure.
Updated by tjyrinki_suse almost 3 years ago
- Related to action #81266: Improve output of zfs test failure added
Updated by tjyrinki_suse almost 3 years ago
- Subject changed from [qe-core][opensuse] test fails in zfs - zfs kernel module not found on Jump to [opensuse] test fails in zfs - zfs kernel module not found on Jump
- Start date deleted (
2020-09-17)
Updated by slo-gin over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 month ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.