action #33082
closed[sle][functional][u] sysauth/sssd is not scheduled on osd
100%
Description
Motivation¶
There is a test module "sysauth/sssd" which is scheduled on o3 but not on osd anywhere.
Acceptance criteria¶
- AC1: sssd is scheduled in SLE tests or we have very good reasons documented why it can not be run there with an alternative testing approach for sssd on SLE
Suggestions¶
- Check if the sssd test module can be run on SLE
- Make sure to cover both SLE12+SLE15 codestreams
- Optional: If the module does not work on sssd adapt or come up with followup task in another ticket
Updated by okurz over 6 years ago
- Blocked by action #31246: [functional][u][bsc#1085145]test fails in sssd: use of deprecated python-pam added
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][u]sysauth/sssd is not scheduled on osd to [sle][functional][u] sysauth/sssd is not scheduled on osd
- Target version changed from Milestone 17 to Milestone 21+
Updated by okurz over 6 years ago
- Target version changed from Milestone 21+ to Milestone 21+
Updated by okurz almost 6 years ago
- Related to action #44141: [functional][u][leap] test fails in sssd in junit test step "Start SSSD" added
Updated by okurz almost 6 years ago
- Blocks action #13168: [qe-core][opensuse][sle][functional] Sudo and LDAP/SSSD for sudoers added
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21+ to Milestone 24
Updated by okurz over 5 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by dheidler over 5 years ago
These changes are needed to execute the sssd module on sle15 - but the testsuite will still fail.
diff --git a/tests/sysauth/sssd.pm b/tests/sysauth/sssd.pm
index 94d4622b9..1b0783ce1 100644
--- a/tests/sysauth/sssd.pm
+++ b/tests/sysauth/sssd.pm
@@ -16,12 +16,24 @@ use strict;
use testapi;
use utils;
use version;
+use version_utils;
sub run {
# Assume consoletest_setup is completed
select_console 'root-console';
- if (is_sle) {
- assert_script_run 'source /etc/os-release';
- if (is_sle '>=15') {
- if (script_run('SUSEConnect -p PackageHub/${VERSION_ID}/${CPU}', 300) != 0) {
- record_soft_failure 'bsc#1124318 - Fail to get PackageHub Pool Metadata - running the command again as a workaround';
- assert_script_run 'SUSEConnect -p PackageHub/${VERSION_ID}/${CPU}', 300;
- }
- assert_script_run('SUSEConnect -p sle-module-legacy/${VERSION_ID}/${CPU}', 300);
- }
- } + # Install test subjects and test scripts my @test_subjects = qw( python3-python-pam
Updated by okurz over 5 years ago
That's interesting. Are you saying we need phub+legacy to be able to install sssd? Looking for the package "sssd" in 000product of SLE-15-SP1 I can find it referenced in the module basesystem so I don't see why we would need to add the others. Is there some dependency missing?
Updated by okurz over 5 years ago
I tried out using https://github.com/okurz/scripts/blob/master/docker-sle-internal-repos , disabled all repos except SLES, basesystem, desktop-applications, server-applications and sucessfully install sssd
. Are we missing dependencies to actually call the tests maybe?
Updated by zluo over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
Updated by zluo over 5 years ago
for sles 15 sp1
http://f40.suse.de/tests/3311 shows successful test run now.
Updated by zluo over 5 years ago
http://f40.suse.de/tests/3339#step/sssd/28
shows that sssd is installed and junit test got started, but ###junit failure time="2019-04-09T05:18:54.010" type="Failed to authentication testuser1"
For this failure I can file a bug report later.
Updated by zluo over 5 years ago
Updated by zluo over 5 years ago
to check on osd:
http://openqa.suse.de/tests/2791001
https://openqa.suse.de/tests/2791970 (report the issue when it is done)
Updated by zluo over 5 years ago
for issue Failed to authentication testeruser1 I filed a bug report:
Updated by SLindoMansilla over 5 years ago
- Related to action #50204: [functional][u][opensuse] no coverage for sssd and active directory authentication on Leap added
Updated by zluo over 5 years ago
- Status changed from In Progress to Feedback
waiting for merging PR.
Updated by SLindoMansilla over 5 years ago
- Related to action #50336: [sle][functional][u] registration::add_suseconnect_product should handle retries added
Updated by zluo over 5 years ago
The changes of my PR is okay for now:
https://openqa.suse.de/tests/2812575#step/sssd/20 shows the fix is working, but failed at
https://openqa.suse.de/tests/2812575#step/sssd/30
junit test for sles 12 sp5 is not working yet:
See my comment in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7267.
Updated by SLindoMansilla over 5 years ago
- Related to action #50486: [opensuse][functional][u] test fails in sssd - No module name pam added
Updated by SLindoMansilla over 5 years ago
The missing PAM module is related to the change from Python2 to Pyhton3: #50486
I will work on that.
Can this ticket be closed?
Updated by zluo over 5 years ago
- Status changed from Feedback to Resolved
this is already scheduled on osd and for both: sles 12 and sles 15.
see also related https://progress.opensuse.org/issues/50537