Project

General

Profile

action #96513

coordination #96980: [qe-core][samba_adcli][epic] Tracker for samba_adcli failures

[qe-core][sporadic][samba_adcli] wbinfo fails

Added by geor 3 months ago. Updated 26 days ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP3-Server-DVD-Updates-aarch64-mau-extratests2@aarch64-virtio fails in
samba_adcli

Test samba_adcli sporadicly fails due to wbinfo failures
eg wbinfo -u fails with Error looking up domain users

Test suite description

Run console tests against aggregated test repo

Reproducible

Fails since (at least) Build 20210802-1 (current job)

Expected result

Last good: 20210801-1 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues

Related to openQA Tests - action #96512: [qe-core][sporadic] test fails in samba_adcli (fails on ssh to domain)Workable

Related to openQA Tests - action #95611: [qe-core][samba_adcli] test fails in samba_adcli in s390x - adcli join cannot find geeko.com domain Workable2021-07-19

History

#1 Updated by szarate 3 months ago

From the logs:

Aug 02 02:23:06.025123 susetest sssd[10715]: couldn't get address for '10.in-addr.arpa': not found
Aug 02 02:23:06.061348 susetest sssd[10719]: couldn't get address for '10.in-addr.arpa': not found

Aug 02 02:23:30.696529 susetest winbindd[10652]:   kerberos_kinit_password SUSETEST$@GEEKO.COM failed: Client not found in Kerberos database
Aug 02 02:23:34.316645 susetest nmbd[10624]: [2021/08/02 02:23:34.316246,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Aug 02 02:23:34.316764 susetest nmbd[10624]:   *****
Aug 02 02:23:34.316816 susetest nmbd[10624]: 
Aug 02 02:23:34.316868 susetest nmbd[10624]:   Samba name server SUSETEST is now a local master browser for workgroup GEEKO on subnet 10.0.2.15
Aug 02 02:23:34.316913 susetest nmbd[10624]: 
Aug 02 02:23:34.316953 susetest nmbd[10624]:   *****
Aug 02 02:23:36.758834 susetest winbindd[10652]: [2021/08/02 02:23:36.758719,  0] ../../source3/libads/kerberos_util.c:74(ads_kinit_password)
Aug 02 02:23:36.758936 susetest winbindd[10652]:   kerberos_kinit_password SUSETEST$@GEEKO.COM failed: Client not found in Kerberos database
Aug 02 02:23:42.813337 susetest winbindd[10652]: [2021/08/02 02:23:42.813221,  0] ../../source3/libads/kerberos_util.c:74(ads_kinit_password)
Aug 02 02:23:42.813438 susetest winbindd[10652]:   kerberos_kinit_password SUSETEST$@GEEKO.COM failed: Client not found in Kerberos database
Aug 02 02:23:44.971439 susetest systemd[1]: snapperd.service: Succeeded.
Aug 02 02:23:48.867487 susetest winbindd[10652]: [2021/08/02 02:23:48.867333,  0] ../../source3/libads/kerberos_util.c:74(ads_kinit_password)
Aug 02 02:23:48.867598 susetest winbindd[10652]:   kerberos_kinit_password SUSETEST$@GEEKO.COM failed: Client not found in Kerberos database
...

#2 Updated by okurz 3 months ago

  • Related to action #96512: [qe-core][sporadic] test fails in samba_adcli (fails on ssh to domain) added

#3 Updated by okurz 3 months ago

  • Related to action #95611: [qe-core][samba_adcli] test fails in samba_adcli in s390x - adcli join cannot find geeko.com domain added

#4 Updated by geor 2 months ago

  • Subject changed from [qe-core][sporadic] samba_adcli fails (wbinfo -u fails to look up domain users) to [qe-core][sporadic][samba_adcli] wbinfo -u fails to look up domain users

#5 Updated by geor 2 months ago

  • Parent task set to #96980

#6 Updated by geor 2 months ago

  • Subject changed from [qe-core][sporadic][samba_adcli] wbinfo -u fails to look up domain users to [qe-core][sporadic][samba_adcli] wbinfo fails
  • Description updated (diff)

#7 Updated by tjyrinki_suse about 2 months ago

  • Status changed from New to Workable
  • Start date deleted (2021-08-03)

#8 Updated by openqa_review 26 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: mau-extratests2
https://openqa.suse.de/tests/7259279

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Also available in: Atom PDF