action #138989
closed[qe-core] test fails in openldap_configuration
60%
Description
Observation¶
sssd no longer installs a (non-working) sample configuration but leaves this entirely to the user to set up properly
the openldap test basically does copy an own config file in place already - but the directory might not be pre-existing anymore in all cases
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-openldap_to_389ds@64bit fails in
openldap_configuration
Test suite description¶
ldap_to_389ds tools test
Maintainer: wegao@suse.com
Reproducible¶
Fails since (at least) Build 20231101
Expected result¶
Last good: 20231031 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dimstar 6 months ago
https://openqa.opensuse.org/tests/3697288#step/tls_389ds_sssd_client/26
Slightly different test, but the exact same error (directory not pre-existing); there is services::389ds_sssd::config_service();
Updated by dimstar 6 months ago
One more test with the same root cause
https://openqa.opensuse.org/tests/3696801#step/sssd_389ds_functional/36
Updated by josegomezr 6 months ago
- Tags set to bugbusters
- Subject changed from test fails in openldap_configuration to [qe-core] test fails in openldap_configuration
- Status changed from New to In Progress
- Assignee set to josegomezr
- Target version set to QE-Core: Ready
- Parent task set to #123115
I'm investigating.
It also relates to #123115
Updated by dimstar 6 months ago
josegomezr wrote in #note-3:
It also relates to #123115
I don't think they relate.
The issue that shows up today is that sssd no longer creates/populates a non-working /etc/sssd and expects the admin to configure sssd prior to start (which was needed in any case)
As the directory no longer is created by the package, we run into:
cp: cannot create regular file '/etc/sssd/sssd.conf': No such file or directory
creating the directory before adding a file to it should be the fix here
Updated by josegomezr 6 months ago
Waiting for verification runs:
Updated by josegomezr 6 months ago
- Status changed from In Progress to Resolved
All tests are green and PR is merged. Closing this as done!
Updated by dimstar 6 months ago
- Status changed from Resolved to Workable
Reopening - one is incomplete:
https://openqa.opensuse.org/tests/3698131#step/sssd_389ds_functional/54
The issue there being that the sssd.conf file is being downloaded, installed, but not with mode 0600, which makes sssd refuse to start
i.e.:
assert_script_run('mkdir -p /etc/sssd/'); # <-- this we added earlier today
assert_script_run("$docker cp ds389_container:/etc/dirsrv/slapd-frist389/ca.crt /etc/sssd/ldapserver.crt");
assert_script_run("curl " . data_url("sssd/398-ds/sssd.conf") . " -o /etc/sssd/sssd.conf");
The directory is now generated, but sssd.conf is not installed with mode 0600 in this case
Updated by josegomezr 6 months ago
dimstar wrote in #note-10:
Reopening - one is incomplete:
https://openqa.opensuse.org/tests/3698131#step/sssd_389ds_functional/54
The issue there being that the sssd.conf file is being downloaded, installed, but not with mode 0600, which makes sssd refuse to start
i.e.:
assert_script_run('mkdir -p /etc/sssd/'); # <-- this we added earlier today assert_script_run("$docker cp ds389_container:/etc/dirsrv/slapd-frist389/ca.crt /etc/sssd/ldapserver.crt"); assert_script_run("curl " . data_url("sssd/398-ds/sssd.conf") . " -o /etc/sssd/sssd.conf");The directory is now generated, but sssd.conf is not installed with mode 0600 in this case
I got a proposal here: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18126
It should fix the issue and left a little bit of love on the test
Updated by openqa_review 5 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.opensuse.org/tests/3742427#step/java/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.