action #48128
closed
[functional][y] Improve our automatic detection of "no license is shown but expected" and vice versa
Added by okurz about 5 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 24
Description
Motivation¶
In #46613 we needed to handle again one of the common cases that a license is not shown when one is expected (or vice versa). Rodion created bsc#1123057 which also took some rather wasteful steps until the right assignee was reached and the OBS time synced the missing file (or folder). We would like to handle issues like these more efficiently.
In the logs we can check eula_url
.
Acceptance criteria¶
- AC1: At least a post_fail_hook can provide hints what is missing, e.g. file/folder missing in OBS repo
- AC2: The team understood when to expect licenses, e.g. to report better bugs
Suggestion¶
We also could check if product/extension is enabled on scc.suse.com
Find out if we can find or provide hint to the OBS/IBS project which contains license files.
Document the way how to investigate missing license issues and ideally show those hints in openQA. Alternative (easy way out): Tell the team in the ticket or sprint review meeting.
Further details¶
Always latest result in this scenario: latest
- Copied from action #46613: [functional][y] test fails in yast_scc for postreg with sdk - no license is shown added
- Due date set to 2019-03-12
- Description updated (diff)
- Estimated time set to 5.00 h
- Description updated (diff)
Based on the extended suggestions by riafarov I tried to clarify AC2 better and make it simpler
- Assignee set to JERiveraMoya
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
Solution works but cannot be verified in prod due to post_fail_mechanism doesn't behave properly, re-stimate ticket?
- Due date changed from 2019-03-12 to 2019-03-26
- Estimated time deleted (
5.00 h)
- Estimated time set to 5.00 h
I found several things that makes the tests fail in a later stage:
SLE-12-SP5 yast2_scc:
- Add
failok => 1
in console_yasttest
when not finding /var/log/zypper.log
(funny value).
- Comment out gdb logs in
y2logstep
because we are try to install something with zypper when ncurses is still open: "system management locked by the application with pid xxxx".
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
Once OSD is in good shape, I will simulate some failure.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF