action #175434
open
test fails in tls_389ds_sssd_client: needs validation
Added by dimstar about 1 month ago.
Updated 8 days ago.
Category:
Bugs in existing tests
Description
Observation¶
The server confirms that it has generated the user ID for wilber, but the client does not get a successful response.
Talking to the package maintainer, he mentions that this is likely a caching issue, where there is no guarantee on how fast the client will get a correct answer.
Reference https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/6/html/deployment_guide/sssd-cache#sssd-cache
It's likely sufficient to clear caches or possibly restart sssd after generating the users (timing might have changed with the most recent update)
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-security_389ds_sssd_client@64bit fails in
tls_389ds_sssd_client
Test suite description¶
Maintainer: rfan1
Reproducible¶
Fails since (at least) Build 20250113
Expected result¶
Last good: 20250112 (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: security_389ds_sssd_client
https://openqa.opensuse.org/tests/4812221#step/tls_389ds_sssd_client/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: security_389ds_sssd_client
https://openqa.opensuse.org/tests/4851287#step/tls_389ds_sssd_client/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Also available in: Atom
PDF