action #125153
closed[qe-core] test fails in btrfsmaintenance
100%
Description
Observation¶
openQA test in scenario sle-15-SP1-Server-DVD-Updates-x86_64-mau-filesystem@64bit fails in
btrfsmaintenance
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Run filesystem tests against aggregated test repo
Reproducible¶
Fails since (at least) Build nfs_qa_run
Expected result¶
Last good: nfs_qa_run (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by msmeissn over 1 year ago
Problem is that we now release the preset fix to 15-sp1 ltss, the testcase needs to handle it:
Test module: /var/lib/openqa/share/tests/sle/tests/console/btrfsmaintenance.pm
change this:
# Fixed in SP1:Update, but is out of general support
if (is_sle("<15-SP2")) {
to:
if (is_sle("<15-SP1")) {
Updated by maritawerner over 1 year ago
- Subject changed from test fails in btrfsmaintenance to [qe-core] test fails in btrfsmaintenance
Updated by ph03nix over 1 year ago
- Status changed from New to In Progress
- Assignee set to ph03nix
Updated by ph03nix over 1 year ago
- % Done changed from 0 to 40
Updated by ph03nix over 1 year ago
msmeissn wrote:
Problem is that we now release the preset fix to 15-sp1 ltss, the testcase needs to handle it:
Test module: /var/lib/openqa/share/tests/sle/tests/console/btrfsmaintenance.pm
change this:
# Fixed in SP1:Update, but is out of general support
if (is_sle("<15-SP2")) {to:
if (is_sle("<15-SP1")) {
I have a fix which is ready to be deployed, but it still fails in the VRs: https://duck-norris.qe.suse.de/tests/12171#step/btrfsmaintenance/10
When is the update being released to the pipeline?
Updated by msmeissn over 1 year ago
we have the update currently held back, should we push it into the QA queue now?
Updated by ph03nix over 1 year ago
msmeissn wrote:
we have the update currently held back, should we push it into the QA queue now?
Yes you can, we will fix it then once it's there. Which update is it exactly?
Updated by msmeissn over 1 year ago
SUSE:Maintenance:27801
I asked Sergio to push it back into QA now.
Updated by slemke over 1 year ago
msmeissn wrote:
SUSE:Maintenance:27801
I asked Sergio to push it back into QA now.
Hello,
ItÅ› back to the testing queue as:
S:M:27801:291029
Updated by ph03nix over 1 year ago
Thanks. I will check tomorrow and then report back. The fix should be ready.
Updated by ph03nix over 1 year ago
Failing test runs in 15-SP1:
- https://openqa.suse.de/tests/10608805#step/btrfsmaintenance/10 and https://openqa.suse.de/tests/10608793#step/btrfsmaintenance/10
Test runs are only failing on 15-SP1.
Test failure:
Script:
systemctl is-enabled btrfsmaintenance-refresh.service || true
Regular expression:
(?^:enabled)
Output:
disabled
This is IMHO still wrong, the expected output here is static
. Checking the incident and the proposed fix.
Updated by ph03nix over 1 year ago
Got it.
- if
btrfsmaintenance-refresh.path
is enabled, thenbtrfsmaintenance-refresh.service
must be disabled or static. - if
btrfsmaintenance-refresh.path
is disabled, thenbtrfsmaintenance-refresh.service
must be enabled.
Will update the test code accordingly.
Updated by ph03nix over 1 year ago
- % Done changed from 40 to 100
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16504 merged, test runs restarted
Updated by dzedro over 1 year ago
- Status changed from Resolved to Feedback
There is still this failure in incidents.
https://openqa.suse.de/tests/10611915#step/btrfsmaintenance/10
Updated by msmeissn over 1 year ago
the zypper incident does not have the presets update in it, this should go away once we release the presets incident.
Updated by ph03nix over 1 year ago
- Status changed from Feedback to Resolved
dzedro wrote:
There is still this failure in incidents.
https://openqa.suse.de/tests/10611915#step/btrfsmaintenance/10
As Marcus said. I marked the test run as softfailed, since there are no other issues with it.
Updated by dzedro over 1 year ago
27801 is released and btrfsmaintenance test is passing.