action #126617
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
[sporadic] Investigate exportfs in yast2_nfs_server
Description
Motivation¶
Make stable the test
openQA test in scenario sle-15-SP5-Online-aarch64-yast2_ncurses_textmode@aarch64 fails in
yast2_nfs_server
Acceptance criteria¶
AC1: Stabilize yast2_nfs_server by bumping timeout when exporting
AC2: If AC1 is not possible, file a bug with proper steps and find the correct maintainer of the test or maintainer of the package as possible culprit.
Updated by JERiveraMoya over 1 year ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Target version set to Current
Updated by JERiveraMoya over 1 year ago
we need to report this bug to the proper maintainer, so first is to analyze what this test modules really does.
osc maintainer -e could be use to figure out if we find some candidate.
As a maintainer of the test is Maintainer: Fabian Vogt <fvogt@suse.com> who might help.
Updated by JERiveraMoya over 1 year ago
- Subject changed from [sporadic] Bump timeout for command exportfs in yast2_nfs_server to [sporadic] Investigate exportfs in yast2_nfs_server
- Description updated (diff)
Updated by shukui over 1 year ago
Updated by JERiveraMoya over 1 year ago
- Related to action #128648: [Timebox:8h][sporadic] Investigate export failure in yast2_nfs_server added
Updated by JERiveraMoya over 1 year ago
It didn't work, I create another follow-up to give someone else the opportunity to try.
Did we contact the maintainer, if so, please add the answer to that other ticket as information.
Updated by shukui over 1 year ago
The latest are passed, I don't know if we should increase the RAM again or it's due to other performance issues. https://openqa.suse.de/tests/11029331,
https://openqa.suse.de/tests/11029430
Updated by JERiveraMoya over 1 year ago
shukui wrote:
The latest are passed, I don't know if we should increase the RAM again or it's due to other performance issues. https://openqa.suse.de/tests/11029331,
https://openqa.suse.de/tests/11029430
yes, I restarted in the morning, but the previous runs of the same build still contain the same issue.
It is an sporadic issue, cannot be resolved with one run successful.