action #89479
Updated by szarate about 3 years ago
## Observation openQA test in scenario sle-15-SP3-Online-x86_64-extra_tests_textmode_phub@64bit fails in [sssd](https://openqa.suse.de/tests/5646951/modules/sssd/steps/22) In the past, sssd used to be tested using tests/sysauth/sssd.pm testing is currently broken on 15-SP3 with python-pam module, however it's unmantained module not found: https://openqa.suse.de/tests/5421585#step/sssd/28 and it belonged https://openqa.suse.de/tests/5554112#step/sssd/22 . It should have been available in the package hub repo, see PackageHub, but not anymore in 15-SP3. See https://bugzilla.suse.com/show_bug.cgi?id=1180120 for more information about python-pam. It is still affecting other teams like [public cloud](https://progress.opensuse.org/issues/88736), also broken on 15-SP2 in public cloud tests similarly and was disabled there according to https://progress.opensuse.org/issues/88736, but on 15SP2 it is still being run for maintenance test repo and passing at https://openqa.suse.de/tests/5636854 In the end, this might OpenLDAP itself is in Legacy in 15-SP3 and will be a complete rewrite of the sssd tests, rendering tests/sysauth/sssd.pm useless. A bit of background, those tests are a bit extensive removed in 15-SP4 having been replaced by 389-ds, but they were written by a developer that it is long gone from widely used and should continue to be tested in 15-SP3 and earlier SLE versions. In the company, investing time QE Core planning meeting it was suggested to use pam as done in fixing or looking for an alternative the new 389-ds test, which calls pam-config to python-pam and rewrite enable sssd. However, the sssd test suite this ticket is about has data/sssd-tests/pamtest.py which does a bit more expensive than switching to directly testing the service against the system (by means of directly using pam/passwd/getent) just enable sssd, so simply calling pam-config would not be enough. ## Reproducible Fails since (at least) Build [14.2](https://openqa.suse.de/tests/4559227) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=extra_tests_textmode_phub&version=15-SP3) ## Suggestions Follow the approach used by [this](https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12075/files#diff-4e63d910050359ba446d37c691c72c4a4ee4fc8ae8c2b98d00996804e2bdb55dR91) pr, Ideally, dependencies would be adapted so that sets up the Directory Service (389-ds it doesn't need package hub and sssd test module can be scheduled in this case, but there's also the information for openldap). extra_tests_textmode instead. ## Acceptance criteria AC1: sssd is being tested tests using openldap passes on 15SP3, functionally equivalent to current testing but without other dependencies than pam for all codestreams (openSUSE and SLE) using Package Hub (but using Legacy module to get OpenLDAP if needed - to be checked whether it's really gone from Basesystem now) AC2: Move sssd tests from extra_tests_textmode_phub to extra_tests_textmode likewise 15SP2 tested, without Package Hub and without Legacy AC3: ping public cloud testers to tell them how they could re-enable sssd testing on public cloud (Or team is informed that they can be re-enabled) ### Followup during review See how https://progress.opensuse.org/issues/89320 was implemented AC4: Move tests out from extra_tests_textmode_phub and evaluate whether a subticket is needed similar to unify the testing strategy or they are tackling two different approaches non-phub extratests