action #112271
closed
Investigate failure in yast_users on MU
Added by JRivrain almost 2 years ago.
Updated almost 2 years ago.
Description
Observation¶
We tried adding TIMEOUT_SCALE=3, it did not help, we need to figure out what is going on here.
openQA test in scenario sle-12-SP3-Server-DVD-Updates-x86_64-mau_extratests_yast_cmd@64bit fails in
yast_users
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Run console tests against aggregated test repo
Reproducible¶
Fails since (at least) Build 20220609-1 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Project changed from openQA Tests to qe-yam
- Priority changed from Normal to High
- Subject changed from Inverstigate failure in yast_users on MU to Investigate failure in yast_users on MU
- Status changed from New to Workable
- Target version set to Current
- Status changed from Workable to In Progress
- Assignee set to JRivrain
So what happens is this: ypwhich is a tool that "return[s] name of NIS server or map master". But it sometimes returns the IP address of the hostname.
This could be considered as a bug, but:
- I could not reproduce it manually
- it does not return the server's name but still returns the nis server, so not a big deal
- probably changed upstream as we can't see this on sle 15+
So I'd rather not report it as it would probably just waste everyone's time.
- Status changed from In Progress to Feedback
Set to feedback, feel free to take-over if the fix is not satisfactory.
- Status changed from Feedback to Closed
Also available in: Atom
PDF