action #126488
closedcoordination #130072: [epic] Handle openQA adaptions in Yam squad - SLE 15 SP6
[Research: 16h] Test stuck at 'Writing NIS configuration' in nis_client
0%
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-x86_64-nis_client@rakoenig/os-autoinst-distri-opensuse#fix_nis_timeout@64bit fails in
nis_client
latest
The progress bar for "Starting services..." seems to be stuck at 50% for 5 minutes in that screenshot.
Reproducible¶
Problem happens sporadically. The link above is from a quick test if increasing the timeout from 120 seconds to 300 seconds
can solve this issue, but it showed up again in the 3rd test run.
Acceptane criteria¶
- AC1: Investigate the root cause of this problem.
- AC2: If possible find a way to mitigate this.
Files
Updated by rainerkoenig almost 2 years ago
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests)
Updated by rainerkoenig almost 2 years ago
- Subject changed from [Investigate] Test stuck at 'Writin NIS configuration' in nis_client to [Investigate] Test stuck at 'Writing NIS configuration' in nis_client
Updated by syrianidou_sofia over 1 year ago
- Description updated (diff)
- Status changed from New to Workable
Updated by JERiveraMoya over 1 year ago
- Subject changed from [Investigate] Test stuck at 'Writing NIS configuration' in nis_client to [Research: 16h] Test stuck at 'Writing NIS configuration' in nis_client
- Priority changed from Normal to Low
- Target version set to Current
- Parent task set to #130072
Let's tackle this before SP6 in case the sporadic issue is still there.
Updated by tinawang123 over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by tinawang123 over 1 year ago
Rerun the case 14 times.
Only one failed. Related case: https://openqa.suse.de/tests/11572660
Added workaround code to check the result.
Updated by tinawang123 over 1 year ago
The network has some problem
Need return case later: https://openqa.suse.de/tests/11593724#step/nis_client/35
Updated by tinawang123 over 1 year ago
Updated by tinawang123 over 1 year ago
- Status changed from In Progress to Resolved