action #13168
open[qe-core][opensuse][sle][functional] Sudo and LDAP/SSSD for sudoers
0%
Description
Motivation¶
ldap/sssd functionality is an important use case for SLES so we should ensure this is well covered in automatic tests (does not need to be openQA).
Suggestions¶
- Crosscheck coverage of existing openQA/IBS-userspace-regression/slenkins tests we have to test "sudo", "openldap", "sssd"
- Ensure we have an automatic test that does the following steps:
- install sudo, openldap2 and sssd packages
- configure LDAP to synchronize sudoers
- configure SSSD to cache LDAP sudoers rules
- verify it works
Updated by okurz over 7 years ago
We have tests/sysauth/sssd.pm so a start, at least :-)
Updated by okurz over 7 years ago
- Subject changed from Sudo and LDAP/SSSD for sudoers to [opensuse][sle][functional]Sudo and LDAP/SSSD for sudoers
Updated by okurz about 6 years ago
- Subject changed from [opensuse][sle][functional]Sudo and LDAP/SSSD for sudoers to [opensuse][sle][functional][u] Sudo and LDAP/SSSD for sudoers
@scarabeus_iv do you plan to work on this? If we would ask the team QSF-u (QA SLE Functional u-team) to do it I estimate we will not have it within the next months but we could try still :)
Updated by scarabeus_iv about 6 years ago
Not really, Maybe I misclicked when I was creating the ticket. I opened the bug when we were discussing what should be automated with QAM people.
Updated by okurz about 6 years ago
- Description updated (diff)
- Assignee deleted (
scarabeus_iv)
I see, so I guess it makes sense to keep this ticket on the backlog of "[functional][u]" and "[qam]" and unassign you and then we can see which team might be able to pick this up first if any
Updated by okurz about 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
- Blocked by action #33082: [sle][functional][u] sysauth/sssd is not scheduled on osd added
Updated by okurz almost 6 years ago
- Status changed from New to Blocked
- Assignee set to okurz
Updated by okurz over 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by SLindoMansilla about 5 years ago
- Related to action #57215: [functional][u] test fails in sssd - Failed to start SSSD added
Updated by szarate over 4 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
mgriessmeier) - Priority changed from Low to Normal
- Target version changed from future to Milestone 31
We need to check, and take a look how the current sssd test module is doing, also take into account that it is on the phub module, and also we can think about a authentication test scenario
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [opensuse][sle][functional][u] Sudo and LDAP/SSSD for sudoers to [qe-core][opensuse][sle][functional] Sudo and LDAP/SSSD for sudoers
Updated by szarate over 3 years ago
- Related to action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam added
Updated by okurz about 3 years ago
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by okurz about 3 years ago
- Priority changed from High to Normal
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".
Updated by maritawerner about 3 years ago
@szarate: all related tickets are resolved besides the "parent ticket". Could we close this ticket or is there still something to do?
Updated by slo-gin almost 2 years ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin 8 months ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.