action #96512
coordination #96980: [qe-core][samba_adcli][epic] Tracker for samba_adcli failures
[qe-core][sporadic] test fails in samba_adcli (fails on ssh to domain)
0%
Description
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-Incidents-x86_64-mau-extratests2@64bit fails in
samba_adcli
Test suite description¶
Run console tests against aggregated test repo
Reproducible¶
Fails since (at least) Build :20666:webkit2gtk3 (current job)
Expected result¶
Last good: :4705:fetchmail (or more recent)
Further details¶
Always latest result in this scenario: latest
Related issues
History
Updated by #2
Updated by okurz 6 months ago
Updated by - Related to action #96513: [qe-core][sporadic][samba_adcli] wbinfo fails added
#3
Updated by okurz 6 months ago
- Priority changed from Normal to Urgent
Seeing this in couple of tests e.g. https://openqa.suse.de/tests/6640016 and https://openqa.suse.de/tests/6623775 . As it's sporadic I consider it "urgent" as label carry over does not work. Consider https://github.com/os-autoinst/scripts/blob/master/README.md#auto-review---automatically-detect-known-issues-in-openqa-jobs-label-openqa-jobs-with-ticket-references-and-optionally-retrigger to address urgency
#4
Updated by okurz 5 months ago
Proposing removing the test module for now from mau-extratests2 in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13072 to address the urgency
Updated by #7
Updated by okurz 5 months ago
- Priority changed from Urgent to Normal
Discussed in weekly QE sync together. This ticket showed up violating the SLO for urgent tickets. We agreed that the ticket is actually not urgent according to these criteria. See https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives for details
#8
Updated by tjyrinki_suse 4 months ago
Updated by - Status changed from New to Workable
- Start date deleted (
2021-08-03)
#9
Updated by tjyrinki_suse about 1 month ago
- Target version set to QE-Core: Ready
Would be nice to work on samba_ad issues (or at least find out which tasks are relevant at the moment) for the next sprint.