Actions
action #109473
closed[qe-core] test fails in sssd_389ds_functional - Improve error reporting in the docker container
Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-04-05
Due date:
% Done:
0%
Estimated time:
Difficulty:
Sprint:
QE-Core: April Sprint (Apr 13 - May 11)
Tags:
Description
Observation¶
The sssd tests seem to working really well, however, when something goes wrong inside the container, we don't know what's going on, beyond the message shown in the console.
AC¶
- Steps describing how to get the logs from the failing container exist at least for the
execcommand are documented in this ticket - Test uploads the execution logs on failure as part of the post fail hooks
- Root cause is identified and Maintenance has taken action
- [optional]: Document the action taken by Maintenance.
Suggestions¶
- Investigate how to extract the logs of the docker container when the command is
exec, via hooks or - Find out which update was creating the conflict, or what changes happened that caused the test to start failing and notify to #team-lsg-qe-openqa-review on slack
- Improve further logging mechanisms to ensure easier investigation in the future
openQA test in scenario sle-15-SP3-Server-DVD-Updates-aarch64-sssd_389ds_functional@aarch64-virtio fails in
sssd_389ds_functional
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: QE Core / QE Security
Reproducible¶
Fails since (at least) Build 20220405-1
Expected result¶
Last good: 20220404-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Files
Actions