action #52580: [sle][functional][y][timeboxed:20h] test fails in yast2_nfs_client - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

action #52580

closed

[sle][functional][y][timeboxed:20h] test fails in yast2_nfs_client

Added by JERiveraMoya almost 5 years ago. Updated almost 5 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

oorlov

Category:

Bugs in existing tests

Target version:

SUSE QA - Milestone 26

Start date:

2019-06-05

Due date:

2019-07-16

% Done:

Estimated time:

Difficulty:

Description

Observation¶

openQA test in scenario sle-12-SP5-Server-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_nfs_client

Test suite description¶

Maintainer: zluo, riafarov Test for yast2 UI, ncurses only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.

NOTE: we might want to check if module is executed for some versions where nfs client is still 3.
Also, we can consider dropping this check or soften it.

Reproducible¶

Fails since (at least) Build 0178 (current job)
Changes in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7389 seems to break the test. I would require some adjustments.

Expected result¶

Last good: 0170 (or more recent)

Further details¶

Always latest result in this scenario: latest

Actions

Copy link

Updated by riafarov almost 5 years ago

Subject changed from [sle][functional] test fails in yast2_nfs_client to [sle][functional][y] test fails in yast2_nfs_client
Due date set to 2019-07-02
Target version set to Milestone 26

We have same failure for TW, so looks like we simply got ver4 of nfs. But need to check

Actions

Copy link

Updated by okurz almost 5 years ago

Not quite sure what you mean with "we simply got ver4 of nfs". I am pretty sure that NFSv3 in parallel to NFSv4 is supported in all the products that we care about, it's not really "just a new version" of NFS.

Actions

Copy link

Updated by JERiveraMoya almost 5 years ago

It is hardcoded to v3 in the code and probably never tested for sle12sp5.

Actions

Copy link

Updated by pdostal almost 5 years ago

Assignee set to pdostal

Yes, it is hardcoded because of NFSv4 has some significant differences.
By simply looking at the test run I see the NFSv4 is not enabled in the YaST1.

I'm already cloning the job and I will be working on it.
Thank you for reporting

Actions

Copy link

Updated by riafarov almost 5 years ago

Description updated (diff)
Estimated time set to 3.00 h

Actions

Copy link

Updated by okurz almost 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_ncurses
https://openqa.opensuse.org/tests/968369

Actions

Copy link

Updated by riafarov almost 5 years ago

Due date changed from 2019-07-02 to 2019-07-16
Status changed from New to Workable
Assignee deleted (~~pdostal~~)

Hi Pavel, I can see that you don't find time for this one, so we will take over.

Actions

Copy link

Updated by oorlov almost 5 years ago

Status changed from Workable to In Progress
Assignee set to oorlov

Actions

Copy link

Updated by oorlov almost 5 years ago

I've tried to run yast2_nfs4_client module for the failed Test Suites, but it started failing on the 40th line: mutex_wait('nfs4_ready'); The nfs4_ready is not appeared.

So, I'm trying to investigate what was changed in Sle12 Sp5, as according to verification runs, it was passed on SP4.

Actions

Copy link

#10

Updated by riafarov almost 5 years ago

Subject changed from [sle][functional][y] test fails in yast2_nfs_client to [sle][functional][y][timeboxed:20h] test fails in yast2_nfs_client
Estimated time deleted (~~3.00 h~~)

Actions

Copy link

#11

Updated by oorlov almost 5 years ago

After investigation, I've found out that the test was changed to be multi-machine, but we are still expecting execute it as a single-machine test.

Also, NFS version is 4 on SLE12-SP5 and according to discussion with Pavel, yast2_nfs4_client should be used instead. But right now it does not allow to be run on single machine.

Actions

Copy link

#12