action #113351
closed[qe-sap] test fails in sys_param_check
0%
Description
Observation¶
Fails in multiple incident tests, blocking update approval
openQA test in scenario sle-15-SP4-Server-DVD-Incidents-x86_64-mau-sles-sys-param-check@64bit-2gbram fails in
sys_param_check
Test suite description¶
https://gitlab.suse.de/qa-css/sys-param-check
Reproducible¶
Fails since (at least) Build :24921:tiff
Expected result¶
Last good: :24930:sg3_utils (or more recent)
Further details¶
Always latest result in this scenario: latest
Files
Updated by ybonatakis almost 2 years ago
- Status changed from New to In Progress
- Assignee set to ybonatakis
Updated by ybonatakis almost 2 years ago
So the problem looks to be that the first time you invoke yast it prompts you to trust a signing key. For me a zypper ref before invoking yast looks to work.
Updated by ybonatakis almost 2 years ago
I tried also to import it with rpm --import /usr/share/gpg-keys/YaST:Head.pub[0] after some chat with the YaST guys but it didnt work. I will provide a PR with the first option until i get an answer to this one
[0] https://build.opensuse.org/package/view_file/YaST:Head/ci-ruby-container/Dockerfile?expand=1
Updated by ybonatakis almost 2 years ago
Updated by ybonatakis almost 2 years ago
- Status changed from Feedback to Resolved
I see tests passsing. So i resolve this. feel free to reopen it if you find a corner case