Project

General

Profile

Actions

action #109115

closed

[qe-core][qem] test fails in cifs

Added by martinsmac about 2 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-03-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP5-Server-DVD-Updates-x86_64-mau-filesystem@64bit fails in
cifs

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 20220328-1

Expected result

Last good: 20220327-1 (or more recent)

Further details

Always latest result in this scenario: latest

I not found more details in log, only:

wait_serial expected: qr/kb2tN-\d+-/u

Result:

https://openqa.suse.de/tests/8419976#step/cifs/28

mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
kb2tN-32-

And the timeout:
https://openqa.suse.de/tests/8419976#step/cifs/30

# Test died: command 'mount -t cifs -o username=geekotest,password=nots3cr3t,vers=2.0 //currywurst.qam.suse.de/currywurst /mnt/currywurst' failed at /usr/lib/os-autoinst/testapi.pm line 953.
    testapi::_handle_script_run_ret(32, "mount -t cifs -o username=geekotest,password=nots3cr3t,vers=2"..., "fail_message", "", "timeout", 90, "quiet", undef) called at /usr/lib/os-autoinst/testapi.pm line 991
    testapi::assert_script_run("mount -t cifs -o username=geekotest,password=nots3cr3t,vers=2"...) called at sle/tests/network/cifs.pm line 66

Had no logs from journal or dmesg to investigate.
    cifs::run(cifs=HASH(0x55e4b0a977f0)) called at /usr/lib/os-autoinst/basetest.pm line 360
Actions #1

Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qe-core] test fails in cifs to [qe-core][qem] test fails in cifs

Passing since 20220329 again. Infrastructure issue?

Actions #2

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.

Actions #3

Updated by martinsmac about 1 month ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF